ОБ ЭТОМ ЭПИЗОДЕ
Share Episode
Pushkar Gopalakrishna, Senior Staff Software Engineer at Snap, previously Cruise and AWS, joins to explore why engineering organizations pivot away from Terraform and HCL toward Kubernetes-native tools even when they might not be better. We unpack how developer friction, copy-pasted control structures, and misaligned organizational incentives create massive tech debt—often forcing SREs to manually update infrastructure repositories for compliance, resulting in broken pipelines and severe operational friction.
We debate over the mechanics of Crossplane, detailing how its continuous reconciliation loop and Custom Resource Definitions (CRDs) allow teams to express cloud infrastructure as YAML alongside their application manifests at potentially the cost of async validation. Pushkar pulls back the curtain on how Cruise managed infrastructure at scale using a custom internal platform called 'Juno' to bootstrap GCP projects, repositories, and permissions, while leveraging Crossplane for application-level resources. We also dive into the dangers of using CI tools for continuous deployment, detailing a terrifying incident where a pipeline bug accidentally marked three production Kubernetes namespaces for deletion, and how moving to ArgoCD and Argo Rollouts helped prevent future outages for autonomous vehicles.
Finally, we touch on the realities of non-production environment isolation, testing against live APIs, and why platform teams must balance providing a seamless developer experience without stripping away developer accountability.
💡 Notable Links:
- Crossplane
- Podcast Guest Request for Principal Engineer — What work are you doing?
- Amazon Multi-level fullyment center for drones
- ✨ Episode: Terraform vs OpenTofu
- Warren - Books: The Murderbot Diaries
- Pushkar - DJI mini drone
РАСШИФРОВКА 🔗
Welcome back to Adventures in DevOps. It's already been three years since the community discarded HashiCorp for their devious practices, and engineering orgs everywhere have been on the lookout for TF alternatives. I know for us at Authorist, CloudFormation will always hold a special place in my company's hearts when it should have probably been let go a long time ago. But we've recently taken a cleared preference towards OpenTOFU, I think, for what it's worth, the spiritual…
