DevOps Daily with Fexingo: CI/CD, Kubernetes, and Modern Software Operations

Fexingo

Lucas and Luna dissect the daily realities of DevOps, from CI/CD pipeline design to Kubernetes cluster management and the human systems that keep software running. Each episode grounds abstract principles in real incidents—a failed deployment at a major retailer, a postmortem from a cloud outage, a configuration drift disaster—and traces the operational decisions that turned them around. Lucas brings the technical precision of a working engineer, while Luna pushes on the team dynamics, cost trade-offs, and organizational bottlenecks that separate resilient operations from fragile ones. They discuss monitoring strategies, incident response playbooks, infrastructure-as-code trade-offs, and the cultural friction between development velocity and operational stability—always with concrete examples, never with buzzwords. This is the show for engineers, SREs, and platform leads who want to hear two seasoned practitioners argue through the hard choices: when to rewrite vs. patch, how much observability is enough, and how to keep a multi-cloud deployment from becoming a management nightmare. By the end, you'll carry away a sharpened question about your own stack and a new way to think about reliability. #DevOps #CICD #Kubernetes #SiteReliabilityEngineering #PipelineAutomation #InfrastructureAsCode #IncidentResponse #Monitoring #Observability #CloudOperations #ContainerOrchestration #Postmortem #DeploymentStrategy #Technology #FexingoBusiness #BusinessPodcast #SoftwareEngineering #PlatformEngineering Keep every episode free: buymeacoffee.com/fexingo

  1. 1d ago

    Why Kubernetes Horizontal Pod Autoscaler Scaling Decisions Lag

    In this episode of DevOps Daily, Lucas and Luna dig into one of the most misunderstood components in Kubernetes: the Horizontal Pod Autoscaler's default behavior. They explain why HPA scaling decisions can take two to three minutes to take effect, even when CPU or memory spikes suddenly. Using a case study from a mid-size e-commerce platform that saw checkout latency double during a flash sale, they walk through the key knobs—sync period, stabilization window, and scaling tolerance—that operators often leave at defaults. They also share a practical configuration change that cut the platform's scale-up delay from four minutes to under sixty seconds, without sacrificing stability. If you've ever watched a Kubernetes deployment struggle under a traffic spike and wondered why the HPA didn't react faster, this episode gives you the specific parameters to tune. #Kubernetes #HorizontalPodAutoscaler #HPA #Scaling #DevOps #SiteReliabilityEngineering #CloudNative #PerformanceTuning #ECommerce #PodScaling #K8sOperations #ScalingDelays #StabilizationWindow #ClusterAutoscaler #Technology #BusinessPodcast #FexingoBusiness #DevOpsDaily Keep every episode free: buymeacoffee.com/fexingo

    Why Kubernetes Horizontal Pod Autoscaler Scaling Decisions Lag

  2. 1d ago

    Kubernetes Pod Disruption Budgets Cause Unplanned Outages During Voluntarily Evictions

    Episode 129 of DevOps Daily with Fexingo dives into a subtle but dangerous Kubernetes behavior: PodDisruptionBudget violations during voluntary evictions. Lucas and Luna walk through a real incident where a cluster running a critical payment service on 3 replicas with minAvailable=2 saw a complete outage during a node drain. The problem? The PDB only counts pods that are healthy according to readiness probes — but the operator assumed all 3 were eligible. When one pod had a stale ready state and another was being recreated, the eviction controller allowed the drain to proceed, dropping below the minimum. The hosts explain how PDBs interact with readiness gates, why 'voluntary disruption' is misleading, and a concrete fix: use maxUnavailable instead of minAvailable, and always combine with PodHealthyPolicy. No hot takes — just an operational war story that could save your next maintenance window. #Kubernetes #PodDisruptionBudget #SRE #DevOps #NodeDrain #VoluntaryEviction #ReadinessProbe #PodHealthyPolicy #maxUnavailable #minAvailable #ClusterOutage #IncidentResponse #K8sScheduling #CloudNative #SiteReliabilityEngineering #FexingoBusiness #BusinessPodcast #Technology Keep every episode free: buymeacoffee.com/fexingo

    Kubernetes Pod Disruption Budgets Cause Unplanned Outages During Voluntarily Evictions

  3. 2d ago

    How Kubernetes OOMKill Taints Actually Crash Your Cluster

    In this episode of DevOps Daily, Lucas and Luna dive into a lesser-known Kubernetes behavior: the OOMKill taint. When a node runs out of memory and the kernel kills a pod, Kubernetes applies a taint that can evict all remaining pods on that node, causing a cascade of failures. They walk through a real-world scenario where a single memory-hungry pod triggered node-level taints, leading to widespread pod evictions and a near-total cluster outage. Lucas explains how kube-controller-manager applies the TaintNodeByCondition with the MemoryPressure condition, and why the default taint effect (NoExecute) can be more destructive than expected. They discuss mitigation strategies: setting resource requests and limits conservatively, using PriorityClass to protect critical workloads, and configuring the kubelet's --eviction-hard thresholds. The episode also covers how to detect OOMKill taints early using Prometheus alerts and kubectl describe node. By the end, listeners will understand why OOMKill is not just a pod-level problem but a node-level risk that demands proactive monitoring and resource governance. #Kubernetes #OOMKill #ClusterReliability #DevOps #CloudNative #NodeTaint #MemoryPressure #PodEviction #kubelet #PriorityClass #Prometheus #ResourceManagement #SRE #ContainerOrchestration #ProductionIncidents #Technology #FexingoBusiness #BusinessPodcast Keep every episode free: buymeacoffee.com/fexingo

    How Kubernetes OOMKill Taints Actually Crash Your Cluster

  4. 2d ago

    How Kubernetes Pod Security Standards Block Supply Chain Attacks

    In DevOps Daily Episode 127, Lucas and Luna explore how Kubernetes Pod Security Standards (PSS) can block common supply chain attack vectors. They dissect a real-world scenario where a compromised container image from a public registry tries to escalate privileges via hostPath mounts. Lucas explains the three PSS levels—Privileged, Baseline, and Restricted—and how migrating from the deprecated PodSecurityPolicy to PSS with admission controllers like Kyverno or OPA Gatekeeper can enforce least-privilege policies. They also discuss the attack path where a malicious sidecar container bypasses classic security scans, and how PSS's 'Restricted' profile catches privilege escalation at admission time. The hosts share migration tips, common pitfalls (like blocking legitimate workloads), and why PSS adoption is accelerating as Kubernetes 1.25+ removes PSP. A must-listen for platform engineers and security-conscious DevOps teams. #Kubernetes #PodSecurityStandards #SupplyChainSecurity #DevSecOps #ContainerSecurity #K8sSecurity #CyberSecurity #CloudNative #AdmissionController #Kyverno #OPAGatekeeper #PodSecurityPolicy #LeastPrivilege #ContainerSupplyChain #TechPodcast #DevOpsDaily #FexingoBusiness #BusinessPodcast Keep every episode free: buymeacoffee.com/fexingo

    How Kubernetes Pod Security Standards Block Supply Chain Attacks

  5. 3d ago

    Why Kubernetes CronJob Timezone Handling Breaks Schedules

    In this episode of DevOps Daily with Fexingo, Lucas and Luna dive into a surprisingly common failure mode in Kubernetes: CronJob timezone handling. Since Kubernetes 1.22, the CronJob controller treats schedule strings as UTC by default, but many operators assume it honors the node or container timezone. This leads to jobs running hours early or late, especially during daylight saving transitions. Lucas walks through a real incident where a UK-based team's daily cleanup job ran at 9 PM instead of 2 AM every March and October, causing overnight resource spikes. They discuss the `timeZone` field added in 1.24, how to verify it in older clusters, and why even helm charts often miss this. Luna shares a horror story of a production database backup job that silently missed windows for months. The episode closes with a practical checklist: always set `timeZone`, test across DST boundaries, and monitor actual run times vs expected. #Kubernetes #CronJob #Timezone #DevOps #CI/CD #CloudNative #SRE #KubernetesCronJob #TimeZoneBug #DaylightSaving #HelmCharts #Kubernetes124 #ProductionIncident #DatabaseBackup #JobScheduling #TechPodcast #FexingoBusiness #BusinessPodcast Keep every episode free: buymeacoffee.com/fexingo

    Why Kubernetes CronJob Timezone Handling Breaks Schedules

  6. 3d ago

    How Kubernetes Watch Events Overload the API Server

    In this episode of DevOps Daily, Lucas and Luna dive into a notoriously overlooked Kubernetes failure mode—API server overload caused by excessive watch events. They break down how controllers, informers, and custom operators all lean on watch-based architectures, and why a single misconfigured watch can cascade into cluster-wide latency or even outages. Through the lens of a real incident at a mid-sized fintech, they explain what happened when a poorly tuned deployment triggered millions of watch events per minute, flooded etcd, and brought the control plane to its knees. Lucas outlines the specific metrics to monitor (watch event rate, request latency, etcd db size) and the architectural patterns—like using DeltaFIFO, filtering with field selectors, and throttling informer resync intervals—that prevent these meltdowns. Luna brings her own war story about a CI/CD operator that hammered the API server during a Helm release, and the two discuss how to audit your cluster for watch-heavy workloads. By the end, listeners will know exactly how to diagnose and prevent one of the most common yet invisible causes of Kubernetes instability. #Kubernetes #APIServer #WatchEvents #Etcd #K8sOperators #InformerPattern #ClusterReliability #DevOps #CI/CD #Fintech #SiteReliabilityEngineering #K8sPerformance #ControlPlane #DeltaFIFO #FieldSelectors #ContainerOrchestration #FexingoBusiness #BusinessPodcast Keep every episode free: buymeacoffee.com/fexingo

    How Kubernetes Watch Events Overload the API Server

  7. 4d ago

    How Kubernetes Vertical Pod Autoscaler Recommends Wrong Requests

    Kubernetes Vertical Pod Autoscaler (VPA) is supposed to right-size container resource requests automatically. But in practice, VPA's recommender often suggests CPU and memory values that lead to pod evictions or wasted capacity. Drawing on real incidents from a mid-2026 production cluster running 50 microservices, Lucas and Luna unpack why VPA's default OOM-aware policy can misinterpret short-lived memory spikes, how its recommendation window of 8 days lags behind traffic patterns, and why the 'lower bound' mode sometimes recommends requests below actual usage. They walk through a specific case where VPA recommended 512 MiB of memory for a Go service that actually needed 1.2 GiB under peak load, causing repeated OOMKills. The episode closes with practical mitigations: setting custom OOM-scoring thresholds, using VPA in 'initial' mode for batch workloads, and combining VPA with Horizontal Pod Autoscaler using resource metrics. Listeners come away with a clear mental model of VPA's blind spots and how to compensate for them. #Kubernetes #VPA #VerticalPodAutoscaler #ResourceRequests #OOMKill #K8sAutoscaling #ContainerSizing #GoService #PodEviction #HPA #ResourceMetrics #ClusterOps #PerformanceTuning #DevOps #Technology #FexingoBusiness #BusinessPodcast #DevOpsDaily Keep every episode free: buymeacoffee.com/fexingo

    How Kubernetes Vertical Pod Autoscaler Recommends Wrong Requests

  8. 4d ago

    How Kubernetes StatefulSet Rolling Update Breaks Persistent Volume Claims

    In this episode of DevOps Daily, Lucas and Luna dive into a subtle but destructive Kubernetes pitfall: StatefulSet rolling updates that orphan PersistentVolumeClaims when the pod template changes. Using a real-world incident at a mid-sized fintech, they walk through how a simple image update triggered PVC detachment, stalled the rollout, and left the cluster in an inconsistent state. They explain the underlying mechanics — how StatefulSet's pod identity logic interacts with PVC templates, why the 'OnDelete' update strategy buys time but doesn't fix the root cause, and what monitoring signals to watch for. Lucas shares a concrete remediation: pre-binding PVCs via volumeClaimTemplates with stable names, and using a custom operator to handle canary updates safely. Listeners will learn one specific configuration pattern to prevent this silent failure, plus a diagnostic command to check for orphaned PVCs after any StatefulSet change. This is a focused, practical episode for anyone running stateful workloads on Kubernetes. #Kubernetes #StatefulSet #PersistentVolumeClaim #RollingUpdate #DevOps #CloudNative #StatefulWorkloads #K8sFailure #PodIdentity #VolumeClaimTemplates #OnDeleteStrategy #Fintech #IncidentResponse #KubernetesTroubleshooting #CI/CD #Technology #FexingoBusiness #DevOpsPodcast Keep every episode free: buymeacoffee.com/fexingo

    How Kubernetes StatefulSet Rolling Update Breaks Persistent Volume Claims
See All (129)

About

Lucas and Luna dissect the daily realities of DevOps, from CI/CD pipeline design to Kubernetes cluster management and the human systems that keep software running. Each episode grounds abstract principles in real incidents—a failed deployment at a major retailer, a postmortem from a cloud outage, a configuration drift disaster—and traces the operational decisions that turned them around. Lucas brings the technical precision of a working engineer, while Luna pushes on the team dynamics, cost trade-offs, and organizational bottlenecks that separate resilient operations from fragile ones. They discuss monitoring strategies, incident response playbooks, infrastructure-as-code trade-offs, and the cultural friction between development velocity and operational stability—always with concrete examples, never with buzzwords. This is the show for engineers, SREs, and platform leads who want to hear two seasoned practitioners argue through the hard choices: when to rewrite vs. patch, how much observability is enough, and how to keep a multi-cloud deployment from becoming a management nightmare. By the end, you'll carry away a sharpened question about your own stack and a new way to think about reliability. #DevOps #CICD #Kubernetes #SiteReliabilityEngineering #PipelineAutomation #InfrastructureAsCode #IncidentResponse #Monitoring #Observability #CloudOperations #ContainerOrchestration #Postmortem #DeploymentStrategy #Technology #FexingoBusiness #BusinessPodcast #SoftwareEngineering #PlatformEngineering Keep every episode free: buymeacoffee.com/fexingo

Information

You Might Also Like