Platform Engineering Podcast

• Using Feature Flags to Tame Complexity with Mike Zorn

  What if changing a single flag could save you from a failed migration, a broken API, or a late-night rollback?Join us as we dive into how feature flags become a practical tool for changing application behavior at runtime, not just toggling UI elements. Cory talks Mike Zorn about real stories from LaunchDarkly and Rippling, covering how teams use flags to ship safely, debug faster, and simplify complex systems.You’ll hear about:Using feature flags to avoid staging overload and ship directly to productionMigrating critical systems and databases with minimal downtime and riskControlling log levels and rate limits for specific customers on the flyManaging flag sprawl so teams do not drown in half-rolled-out featuresExperimenting with AI features, prompts, and models without fully committingIf you’re working on a platform, running critical infrastructure, or just trying to ship faster without breaking everything, this conversation offers concrete patterns you can start using right away.Guest: Mike Zorn, Senior Software Engineer at RipplingMike’s software engineering journey began with an early interest in problem-solving and programming, starting with creating programs on a TI-83 calculator in middle school. After studying mathematics in college, he transitioned into software through an applied math project that required coding, which sparked his interest in engineering as a career. Professionally, he has worked at several product and SaaS companies, including one that was an early LaunchDarkly customer, where they experienced firsthand the challenges of managing feature flags internally. That experience led him to appreciate the value of tools like LaunchDarkly, eventually joining the company himself. Since then, he has contributed across various areas, including focusing on how LaunchDarkly can best adopt its own platform internally to streamline releases and help engineers work more efficiently. His latest adventure has been joining Rippling as a Senior Staff Software Engineer.Mike Zorn, GitHubMike Zorn, EmailRipplingLaunchDarklyLinks to interesting things from this episode:SigNozSignadotOpen Container Initiative“Using Feature Flags to Avoid Downtime During Migrations”Apache Iceberg

  --------  

  43:29

  --------

  43:29
• Policy as Code: Kyverno and Securing Kubernetes at Scale with Jim Bugwadia

  Most Kubernetes security breaches don't come from zero-day exploits - they come from misconfigurations. While your team runs scanners and reviews reports, containers are already running as root, network policies are missing, and compliance violations are piling up across dozens of repositories.Jim Bugwadia, co-founder and CEO of Nirmata and creator of Kyverno, joins Cory to talk about a different approach: policy as code. Instead of asking developers to remember security best practices across every repo, what if your cluster automatically enforced secure defaults and blocked non-compliant deployments before they ever reached production?You'll learn how to start using Kyverno today without breaking your production environment - from running your first audit scan (no installation required) to implementing enforcement mode with exceptions. Jim explains why micro-segmentation matters more than ever, how to automate network policies for every namespace, and why platform teams are using Kyverno for everything from security to cost optimization.Whether you're running one cluster or managing Kubernetes at scale, this conversation offers practical strategies for making security a byproduct of your platform - not an afterthought.Topics covered:Why shift-left security fails and what "shift-down" means for platform teamsHow to implement Kubernetes policy enforcement without grinding deployments to a haltAutomating secure defaults: network policies, resource quotas, and role bindingsThe crawl-walk-run approach to rolling out policies in existing clustersReal-world use cases beyond security: cost optimization and resource managementGuest: Jim Bugwadia, Co-Founder & CEO of Nirmata and creator of KyvernoJim Bugwadia is the Co-founder and CEO of Nirmata, a Kubernetes management platform built for enterprises to simplify and scale cloud-native operations across clouds, data centers, edge, and connected devices. With a mission to democratize cloud-native best practices, Jim brings deep expertise in building large-scale software products and leading high-performing teams. Before founding Nirmata, he led a global consulting team at Cisco, guiding enterprises and service providers on their cloud computing journeys. Earlier in his career, he contributed to innovative products at startups and major companies including Trapeze Networks, Pano Logic, Jetstream, Lucent, and Motorola. A hands-on technologist, Jim continues to code in Go, Java, and JavaScript, reflecting his passion for building in the rapidly evolving world of software.Jim Bugwadia, XNirmataKyvernoLinks to interesting things from this episode:Kyverno Community Repository“Shift-Down Security” PaperOpenReportsPolicy Reporter“The Shai-Hulud npm malware attack: A...

  --------  

  42:21

  --------

  42:21
• Guest Host: Kelsey Hightower - Beyond Pipelines: Infrastructure As Data

  Is your Git repo really the source of truth for infrastructure - or just a suggestion?Guest host Kelsey Hightower sits down with Cory O’Daniel to unpack why many teams hit dead ends with CI/CD for provisioning, where GitOps struggles with drift, and when TicketOps helps or hurts. They explore a different model: infrastructure as data with typed contracts, shared artifacts, and workflows that embed policy, validation, and upgrades from the start. You’ll hear practical ways to reduce cognitive load for developers while giving operations reliable control and better day‑2 levers.You’ll learn:Why pipelines are a poor fit for infra provisioning and what to do insteadHow to reason about drift as a three‑way merge with realityWhen reconciliation helps, and when it breaks production firefightsHow typed contracts and artifacts connect modules and teams without glue scriptsWays to present safer self‑service without requiring everyone to learn TerraformA simple mental model for treating TicketOps as a surface, not the workflowGuest Host: Kelsey HightowerKelsey has worn every hat possible throughout his career in tech and enjoys leadership roles focused on making things happen and shipping software. Prior to his retirement, he was a Distinguished Engineer at Google, where he worked on Google Cloud Platform. He is a strong open source advocate with a focus on building great software as well as great communities around them. He is also an accomplished author and keynote speaker with a knack for demystifying complex topics, doing live demos and enabling others to succeed. When he is not writing code, you can catch him giving technical workshops covering everything from programming to system administration.Guest: Cory O'Daniel, CEO and Co-Founder of Massdriver and Co-Founder of OpenTofuCory has been a software architect and engineer for 20 years, leading up to the founding of MassDriver. He's also a husband and the father of two kids.Cory O'Daniel, XCory O'Daniel, MediumMassdriver, websiteMassdriver, GitHubMassdriver, YoutubeOpen TofuLinks to interesting things from this episode:"Gitopscracy" video

  --------  

  48:51

  --------

  48:51
• Guest Host: Kelsey Hightower - Are CI/CD and GitOps Just Making Things Harder?

  What if your production environment had a live, trustworthy blueprint you could zoom in and out of on demand?Kelsey Hightower guest-hosts a candid conversation with Cory about why CI/CD pipelines and GitOps often break down for cloud infrastructure. They explore a simpler operational model: treat infrastructure as data, lean on clear checkpoints instead of rigid “golden paths,” and make production legible for both developers and ops.You’ll learn:Where CI/CD adds friction for infra and what to do insteadWhy GitOps works for apps but hits limits for databases, networks, and multi-region realitiesHow “living diagrams” help new teammates understand prod on day onePractical guardrails that evolve with your org without locking teams inWays to reduce drift, surprise cloud costs, and Day Two chaosA mindset shift: databases for ops data, not shell-script archaeologyWalk away with concrete patterns to make production understandable, auditable, and easier to change—without more YAML or bigger pipelines.Guest Host: Kelsey HightowerKelsey has worn every hat possible throughout his career in tech and enjoys leadership roles focused on making things happen and shipping software. Prior to his retirement, he was a Distinguished Engineer at Google, where he worked on Google Cloud Platform. He is a strong open source advocate with a focus on building great software as well as great communities around them. He is also an accomplished author and keynote speaker with a knack for demystifying complex topics, doing live demos and enabling others to succeed. When he is not writing code, you can catch him giving technical workshops covering everything from programming to system administration.Guest: Cory O'Daniel, CEO and Co-Founder of Massdriver and Co-Founder of OpenTofuCory has been a software architect and engineer for 20 years, leading up to the founding of MassDriver. He's also a husband and the father of two kids.Cory O'Daniel, XCory O'Daniel, MediumMassdriver, websiteMassdriver, GitHubMassdriver, YoutubeOpen TofuLinks to interesting things from this episode:SigNoz“The $6,459 Terraform Lesson: Why Infrastructure Lifecycle Monitoring Matters” by Liz Fong-Jones "Gitopscracy" video

  --------  

  30:18

  --------

  30:18
• Guest Host: Kelsey Hightower — Why IaC Alone Isn’t Enough

  Ever wonder why strong Terraform modules still lead to long review queues and fragile pipelines? From hand-built scripts and early data center migrations to cloud sprawl and Kubernetes, configuration management has changed a lot - but the core struggle remains: too many decisions, not enough guardrails. Guest host Kelsey Hightower sits down with Cory O’Daniel to unpack where Infrastructure as Code succeeds and where teams get stuck.What you’ll learn:How to avoid “choice overload” in cloud configs by moving decisions upstreamPractical ways to pair IaC with UX, policies, and SLAs to reduce toilWhen click-ops is a symptom, not the problem - and how to replace it safelyPatterns for scaling platform practices beyond a handful of expertsA simple mental model for mapping workflows across serverless, containers, and VMsGuest Host: Kelsey HightowerKelsey has worn every hat possible throughout his career in tech and enjoys leadership roles focused on making things happen and shipping software. Prior to his retirement, he was a Distinguished Engineer at Google, where he worked on Google Cloud Platform. He is a strong open source advocate with a focus on building great software as well as great communities around them. He is also an accomplished author and keynote speaker with a knack for demystifying complex topics, doing live demos and enabling others to succeed. When he is not writing code, you can catch him giving technical workshops covering everything from programming to system administration.Guest: Cory O'Daniel, CEO and Co-Founder of Massdriver and Co-Founder of OpenTofuCory has been a software architect and engineer for 20 years, leading up to the founding of MassDriver. He's also a husband and the father of two kids.Cory O'Daniel, XCory O'Daniel, MediumMassdriver, websiteMassdriver, GitHubMassdriver, YoutubeOpen TofuLinks to interesting things from this episode:"The Phoenix Project: A Novel about IT, DevOps, and Helping Your Business Win" by Gene Kim"15 Years of Duct Tape - Why IaC Adoption Stalled at 30"

  --------  

  39:40

  --------

  39:40

Mais podcasts de Negócios

Podcasts em tendência em Negócios

Sobre Platform Engineering Podcast