In this episode of DevOps Daily with Fexingo, Lucas and Luna dig into a forgotten Kubernetes feature: PodPreset. Once hailed as a way to inject configuration into pods automatically, PodPreset was deprecated in 2022 and removed in Kubernetes 1.25. But many clusters still carry its legacy — and that legacy causes config drift that operators never see coming. Lucas explains how PodPreset worked, why it was retired in favor of admission webhooks and Operators, and how leftover PodPreset admission controller configurations can silently mutate pod specs. He walks through a real incident where a team spent weeks debugging mysterious container restarts, only to trace the root cause to an old PodPreset definition. Luna pushes on whether the Kubernetes ecosystem moves too fast for production stability. The episode ends with a forward-looking question: as Kubernetes sheds beta APIs and legacy features every release, are operators keeping up with the removal notices buried in release notes? If today's tech conversation gave you something usable, support the show at buy me a coffee dot com slash fexingo.

#Kubernetes #PodPreset #ConfigDrift #DevOps #CloudNative #K8s #AdmissionWebhook #OperatorPattern #KubernetesDeprecation #KubernetesMigration #KubernetesReleaseNotes #KubernetesBetaAPI #KubernetesConfigManagement #CI/CD #Technology #FexingoBusiness #BusinessPodcast #DevOpsDaily

Keep every episode free: buymeacoffee.com/fexingo

In this episode of DevOps Daily with Fexingo, Lucas and Luna dive into a subtle but severe Kubernetes anti-pattern: PriorityClass starvation at the node level. They break down a real-world case where a team set a critical batch job's priority too high, causing it to preempt essential daemonsets and system pods, leading to node instability and failed scheduling. Lucas explains how the Kubernetes scheduler's preemption logic interacts with kubelet's resource allocation, why setting priorities without understanding the full hierarchy can backfire, and the three metrics you should monitor — preemption counts, pod eviction rates, and node pressure conditions — to catch starvation before it takes down your cluster. Luna pushes on whether kubectl describe node gives enough information, and they walk through a practical audit using PriorityClass objects and pod spec priority fields. If you've ever wondered why nodes look healthy but pods won't land, this episode gives you the debugging framework. No fluff, just the edge cases that break production.

#Kubernetes #PriorityClass #PodPreemption #Scheduling #DevOps #CloudNative #NodeStarvation #ClusterReliability #kubelet #BatchJobs #DaemonSet #ResourceManagement #KubernetesScheduler #PodEviction #NodePressure #Technology #FexingoBusiness #BusinessPodcast

Keep every episode free: buymeacoffee.com/fexingo

In this episode of DevOps Daily, Lucas and Luna investigate a deceptively common Kubernetes failure: when ingress controller session affinity (sticky sessions) silently breaks during rolling updates. They walk through a real incident at a mid-size e-commerce platform where users were suddenly logged out mid-session after a routine deployment. Lucas explains the mechanics — how NGINX ingress controller uses Pod IP hashing by default, and how a new replica set flips the hash mapping, redirecting users to pods that have never seen their session data. Luna pushes on whether the fix is a readiness probe tweak, an external session store, or a different ingress controller. They also discuss when to use sticky sessions at all, and why session affinity is often a workaround for a deeper architectural issue. Concrete, specific, and immediately applicable for anyone running Kubernetes in production.

#Kubernetes #IngressController #StickySessions #SessionAffinity #RollingUpdate #NGINXIngress #DevOps #SiteReliabilityEngineering #PodLifecycle #SessionManagement #K8sNetworking #ProductionIncident #ECommerce #LoadBalancing #ReadinessProbe #Technology #FexingoBusiness #BusinessPodcast

Keep every episode free: buymeacoffee.com/fexingo

In this episode of DevOps Daily, Lucas and Luna dive deep into Kubernetes audit logs—a powerful but often overlooked tool for detecting silent security threats. They walk through a real-world scenario where a cluster was compromised via a misconfigured webhook, and the only clue was buried in the audit log. They explain how to enable audit logging, what to look for (like unexpected impersonation attempts or suspicious RBAC escalations), and why most teams don't parse these logs until it's too late. The hosts also discuss how audit logs can be integrated with SIEM tools for automated alerting, and share a practical tip: watch for repeated 403 errors—they might indicate an attacker probing your cluster. If you're running Kubernetes in production, this episode will change how you think about observability.

#Kubernetes #AuditLogs #Security #CloudNative #K8s #DevOps #SIEM #RBAC #ThreatDetection #Webhook #Infrastructure #Observability #Technology #FexingoBusiness #BusinessPodcast #DevOpsDaily #Podcast #CyberSecurity

Keep every episode free: buymeacoffee.com/fexingo

Lucas and Luna dive into a subtle Kubernetes anti-affinity trap that many teams don't notice until it's too late. The PodTopologySpread constraint — designed to spread pods evenly across failure domains — can actually concentrate pods onto fewer nodes when misconfigured with a low maxSkew value. Lucas explains a real incident at a mid-sized SaaS company where a three-zone cluster with maxSkew=1 caused a cascade: after one zone failed, the constraint blocked rescheduling because spreading the remaining pods would violate the skew limit. The result was a 50% capacity loss and a six-hour recovery. Luna questions whether the default maxSkew of 1 is too aggressive for most workloads. They walk through the math, the YAML, and the safer defaults — plus when to skip the constraint entirely. If you manage Kubernetes in production, this episode will save you a painful post-mortem.

#Kubernetes #PodTopologySpread #HighAvailability #maxSkew #PodAntiAffinity #DevOps #SiteReliability #ProductionIncident #K8sScheduling #CloudNative #Infrastructure #AvailabilityZones #FailureDomain #ClusterResilience #Technology #DevOpsDaily #FexingoBusiness #BusinessPodcast

Keep every episode free: buymeacoffee.com/fexingo

Lucas and Luna dig into a deceptively common Kubernetes failure: PersistentVolumeClaims stuck in Pending because the WaitForFirstConsumer binding mode delays volume provisioning until a pod actually consumes the claim. They trace how this interacts with StatefulSets, pod topology spread constraints, and cluster autoscaler to create cascading scheduling deadlocks. The episode walks through a real incident at a mid-size fintech where 150 PVCs stayed Pending for 14 hours, delaying an entire batch-processing pipeline. Lucas explains why immediate binding works for most workloads, when WaitForFirstConsumer makes sense, and how to detect these stalls before they hit production. Luna questions whether the Kubernetes docs bury this behavior too deep for teams that don't run storage admin day to day. They close with concrete monitoring and admission-control practices to avoid the trap.

#Kubernetes #PersistentVolumeClaim #WaitForFirstConsumer #Storage #StatefulSet #PodTopologySpread #ClusterAutoscaler #SchedulingDeadlock #VolumeBindingMode #Fintech #BatchProcessing #AdmissionControl #Technology #DevOps #CloudNative #FexingoBusiness #BusinessPodcast #K8sTroubleshooting

Keep every episode free: buymeacoffee.com/fexingo

Lucas and Luna dive into a specific blind spot in Kubernetes cluster observability: the Node Problem Detector (NPD) and how it fails to catch silent hardware and kernel-level issues. They walk through a real incident at a mid-sized fintech where NPD reported 'healthy' while memory corruption was quietly degrading performance across 12 nodes. They explain why default NPD configurations only monitor a handful of conditions, how kernel log parsing gaps create false negatives, and what you can do with custom problem detectors and event exporters. If you run Kubernetes in production, this episode will save you from a nightmare outage that doesn't show up in your usual dashboards.

#Kubernetes #NodeProblemDetector #ClusterObservability #SilentFailures #KernelLogs #MemoryCorruption #Fintech #DevOps #SRE #K8sTroubleshooting #ProductionIncidents #NodeHealth #CustomDetectors #EventExporters #LinuxKernel #Technology #FexingoBusiness #BusinessPodcast

Keep every episode free: buymeacoffee.com/fexingo

In this episode of DevOps Daily with Fexingo, Lucas and Luna dive into a hidden Kubernetes failure mode: when ConfigMap updates are rolled out to Deployments, but the Pods never pick up the new data because the rollout trigger is missing. They walk through a real incident from a mid-sized fintech where a database connection string changed at 2 AM, the ConfigMap was updated, but the Deployment never restarted—causing six hours of silent query failures. They explain why rolling updates depend on annotations or checksums, how immutable ConfigMaps can prevent accidental partial updates, and what to check in your staging pipeline tomorrow. Practical, specific, and rooted in a real outage.

#Kubernetes #ConfigMap #DevOps #K8sRollout #ImmutableConfigMap #CloudNative #SiteReliabilityEngineering #ContinuousDeployment #InfrastructureAsCode #K8sFailureMode #PodRollout #Helm #Kustomize #Technology #DevOpsDaily #FexingoBusiness #BusinessPodcast #SoftwareOperations

Keep every episode free: buymeacoffee.com/fexingo

In this episode of DevOps Daily, Lucas and Luna dive into a subtle but dangerous Kubernetes problem: priority class starvation. When lower-priority pods are preempted but never actually evicted due to PDB constraints, the scheduler gets stuck in a loop, and the cluster can grind to a halt. They walk through a real scenario where a team's production deployment failed because a single PriorityClass name was misspelled, leading to silent resource starvation over 48 hours. Using concrete numbers — 200 pending pods, three priority tiers, and a 30-second scheduler backoff — they explain why default PriorityClasses are a trap, why PDBs block preemption, and how to audit your cluster before it's too late. If you manage Kubernetes clusters, this episode will save you from a Monday morning outage.

#Kubernetes #PriorityClass #PodDisruptionBudget #SchedulerPreemption #ClusterStarvation #DevOps #SiteReliabilityEngineering #CloudNative #K8sOperations #PodLifecycle #ResourceManagement #KubernetesTroubleshooting #PriorityPreemption #InfrastructureEngineering #ContainerOrchestration #Technology #FexingoBusiness #BusinessPodcast

Keep every episode free: buymeacoffee.com/fexingo

Lucas and Luna dig into a surprisingly brittle Kubernetes footgun: using the Downward API to inject pod labels as environment variables. They walk through a real incident where a label change triggered cascading failures because application code was hard-wired to read pod name from an env var that silently went stale. The conversation covers why this pattern is so common in Helm charts, how it differs from using the filesystem volume mount, and a concrete migration path to a more stable approach using the Downward API volume or operator-managed sidecars. If you've ever debugged a pod that couldn't figure out its own name, this episode will save you a late-night incident.

#Kubernetes #DownwardAPI #PodIdentity #Helm #DevOps #CloudNative #Infrastructure #K8sTroubleshooting #PodLabels #EnvironmentVariables #OperatorPattern #Sidecar #IncidentResponse #SoftwareEngineering #DevOpsDaily #FexingoBusiness #BusinessPodcast #Technology

Keep every episode free: buymeacoffee.com/fexingo