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 obse
Pitch Analysis
Required Pod Score for this show. PitchCentric checks your profile against host openness, topical fit, and audience signals before you generate a pitch.
Contact path
Verified email
Booking probability
35%
Guest openness
Selective
Verified email on file
80/100
Required Score
Sign up to generate a grounded pitch for DevOps Daily with Fexingo: CI/CD, Kubernetes, and Modern Software Operations.
What is DevOps Daily with Fexingo: CI/CD, Kubernetes, and Modern Software Operations?
DevOps Daily with Fexingo: CI/CD, Kubernetes, and Modern Software Operations is a business podcast hosted by Fexingo, with 155 episodes on record and a Required Pod Score of 80. PitchCentric scores this show on Booking Probability, Listen Score, and live audience signals refreshed every 24 hours.
About the host
Fexingo hosts DevOps Daily with Fexingo: CI/CD, Kubernetes, and Modern Software Operations, a business show with 155 episodes published.
Our AI reads these to draft pitches. Use them as grounding for a pitch that cites a real guest and a specific topic.
Episode #161
How Kubernetes Metrics Server Latency Breaks HPA Scaling
Aug 20, 20268 minS4
In this episode of DevOps Daily, Lucas and Luna dig into a deceptively simple failure mode: the Kubernetes Metrics Server takes a few extra seconds to return pod metrics, and the Horizontal Pod Autoscaler overreacts. They walk through a real incident where a 45-second metrics delay caused wild replica swings, wasted cloud spend, and a brief outage. Lucas explains how the HPA's default tolerance window interacts with the Metrics Server's 15-second scrape interval and why a simple misconfiguration can turn a steady workload into a yo-yo. They discuss how to monitor metrics-server latency, the role of the --horizontal-pod-autoscaler-sync-period flag, and why tuning your autoscaler's behavior to actual metrics freshness is more important than chasing the latest feature. Along the way, they tie the lesson to the broader principle: in Kubernetes, the control plane's speed dictates your application's stability. A short, honest word about listener support keeps the show ad-free, then it's back to the metrics trench. #Kubernetes #HorizontalPodAutoscaler #MetricsServer #DevOps #SRE #CloudNative #Scaling #Observability #Prometheus #ContainerOrchestration #Infrastructure #Performance #IncidentManagement #TechPodcast #FexingoBusiness #BusinessPodcast #Technology #DevOpsDaily Keep every episode free: buymeacoffee.com/fexingo
How Kubernetes Finalizers Locked Our Namespace for Three Weeks
Aug 19, 20268 minS4
In Episode 160 of DevOps Daily, Lucas and Luna drill into a deceptively simple Kubernetes footgun: object finalizers and namespace deletion. When a team at a mid-sized fintech tried to clean up a failed release, a single finalizer on a custom resource (CRD) silently held the namespace in 'Terminating' for three weeks. The episode walks through exactly how finalizers work under the hood, why the namespace didn't just vanish, how they finally traced it via kubectl and the API server logs, and the three guardrails they now enforce: auditing finalizers before deletion, using kubectl patch to remove them only when safe, and linting CRDs to block finalizers that don't self-heal. Lucas and Luna also discuss when a finalizer is worth keeping (like for cleanup jobs) versus when it becomes a footgun, and they stress-test a couple of common workarounds. No fluff, just a real ops story with concrete commands you can use today. #Kubernetes #Finalizers #Namespaces #CRD #DevOps #CloudNative #Troubleshooting #kubectl #APIServer #ClusterOps #SRE #Fintech #ProductionIssue #TechOps #CloudInfrastructure #DevOpsDaily #FexingoBusiness #BusinessPodcast Keep every episode free: buymeacoffee.com/fexingo
How Kubernetes Object Finalizers Block Namespace Deletion
Aug 18, 20268 minS4
In this episode of DevOps Daily, Lucas and Luna dig into a surprisingly common Kubernetes headache: namespaces stuck in the Terminating state because of object finalizers. They walk through a real incident where a single stuck custom resource with a finalizer held up an entire namespace deletion, blocking a whole environment teardown and causing pipeline failures. You'll learn what finalizers actually do, how they can silently break cluster cleanup, and the step-by-step debugging approach — from checking finalizers with kubectl to patching or force-deleting when needed. They also discuss safe alternatives and when it's better to fix the controller instead of bypassing the safety mechanism. This episode gives you a concrete mental model and a few kubectl commands you'll actually use in production. #KubernetesFinalizers #NamespaceDeletion #K8sOperators #CloudNative #DevOps #KubectlTips #ClusterCleanup #KubernetesTroubleshooting #ControllerDesign #CustomResourceDefinitions #TechPodcast #FexingoBusiness #BusinessPodcast #Technology #SoftwareEngineering #InfrastructureAsCode #SiteReliabilityEngineering #CloudInfrastructure Keep every episode free: buymeacoffee.com/fexingo
When a Kubernetes node reboots for a kernel update or hardware maintenance, pods don't just vanish and come back cleanly. The kubelet marks them as terminated, the container runtime loses state, and what looks like a routine maintenance window turns into failed readiness probes, stuck terminating pods, and a cascade of restarts. In episode 158 of DevOps Daily, Lucas and Luna break down the actual mechanics of node reboot behavior: how the kubelet handles graceful shutdown, why container runtimes like containerd and CRI-O can orphan processes, and why your deployment's restartPolicy is the hidden variable that decides whether that reboot is a blip or a production incident. They also walk through a real scenario where a node reboot during off-peak hours caused a payment service to restart with cold caches, triggering a 5x latency spike. If you've ever wondered why your pods don't come back the way they left, or why a simple reboot feels like playing roulette with your uptime, this episode gives you the mental model and the practical mitigations: preStop hooks, terminationGracePeriodSeconds, and podDisruptionBudgets that actually work. #Kubernetes #NodeReboot #Kubelet #ContainerRuntime #PodRestart #DevOps #SRE #CloudNative #Containerd #CRIO #PreStopHook #TerminationGracePeriod #PodDisruptionBudget #SiteReliability #Infrastructure #Tech #FexingoBusiness #BusinessPodcast Keep every episode free: buymeacoffee.com/fexingo
How Kubernetes Node Journal Rotation Hides Crash Loops
Aug 16, 20269 minS4
In this episode of DevOps Daily, Lucas and Luna dig into a silent killer in Kubernetes clusters: systemd journal rotation. When the kubelet's logs are rotated out before a crash is captured, debugging becomes guesswork. They walk through the mechanics of journald's size and time-based rotation, the systemd-journald daemon's default rate limits, and how a busy cluster can lose critical kubelet logs in seconds. They share a real-world scenario where a node crash loop went unnoticed for hours because the logs were gone. They also discuss practical fixes: setting SystemMaxUse and RuntimeMaxUse, adjusting RateLimitIntervalSec, forwarding logs to a central aggregator, and using node problem detector to catch issues early. By the end, you'll know exactly how to ensure your kubelet logs survive the next incident. #Kubernetes #DevOps #Systemd #Journald #LogRotation #Kubelet #CrashLoop #Troubleshooting #SiteReliability #CloudNative #Observability #Logging #NodeProblemDetector #IncidentResponse #TechPodcast #Business #FexingoBusiness #Podcast Keep every episode free: buymeacoffee.com/fexingo
Every question we get asked before someone starts their trial.
If you have a concern about deliverability, AI quality, data privacy, or whether this will actually work for your specific situation, it's probably answered below.
What is the difference between Founder Solo and Founder Pro?
Founder Solo gives you 50 AI pitches per month using the credit model (Standard pitches cost 1 credit, Enriched pitches cost 2). Founder Pro raises that to 200 credits per month and adds full Booking Probability access, unlimited Magic Match, Apollo enrichment credits, and data export capabilities. Both plans use the same credit system, so you can stretch your monthly budget further by using Standard-mode drafting.
How do agency tiers work?
Agency tiers have no base fee. You pay per managed client and per talent profile. Agency Standard is $199 per client per month; Agency Pro is $399 per client per month. Both add $39 per talent profile per month. Your own team's user seats are always free.
What is a talent profile?
A talent profile represents one person (founder, executive, or spokesperson) you are booking onto podcasts. It includes their bio, topics, headshots, and outreach history. Team plans include 5 profiles; agency plans are pay-as-you-go.
Can I switch plans later?
Yes, at any time. Upgrades take effect immediately; downgrades apply at the end of the current billing period. Contact support if you need help migrating between plan families.
Do you offer a free trial?
Every paid plan includes a 15-day free trial. Your card is saved at signup but you will not be charged until day 16. Cancel any time from your dashboard.
What happens if I cancel?
You keep access until the end of your current billing period. No charges after that. Your data is retained for 30 days in case you reactivate.
Is the 20% annual discount automatic?
Yes. Select Annual on the pricing toggle and the discounted price is applied automatically at checkout. The annual price shown is the full year cost.
What if I have more than 50 profiles or 20 clients?
That is our Enterprise tier. Contact our sales team and we will build a custom plan with volume pricing, a dedicated account manager, and SLA guarantees.
