Relying on numerous CI/CD pipelines for infrastructure management creates complexity and is not ideal for resources with a lifecycle.
Infrastructure management evolved from manual shell scripts to configuration management and finally to API-driven Infrastructure as Code tools like Terraform.
Infrastructure as Code tools are one-shot executors that don't continuously manage state, leading to configuration drift where reality diverges from code.
Kubernetes can be used as a universal control plane because its orchestration capabilities are extensible beyond its native resources.
Crossplane extends Kubernetes to manage external cloud resources through providers and custom composite resources, enabling continuous reconciliation to prevent drift.
Use a GitOps operator like Argo CD to automatically sync resource definitions from a Git repository to the Kubernetes control plane for declarative management.
A practical demonstration shows how a Git commit triggers Argo CD and Crossplane to provision a Kubernetes cluster, an API Gateway, and a DynamoDB table.
Overcome the initial chicken-and-egg problem by using a temporary Kubernetes cluster to provision the permanent control plane, then migrating the state to make it self-managing.
The Q&A session covers topics like resource recovery after a control plane failure, schema versioning, and strategies for migrating from Terraform to Crossplane.
29:21Um e Habiba
42:45Marc Nimmerrichter
21:43Mario Valderrama
44:13Robert Hoffmann
40:00Rob Richardson
57:24Hannes Norbert Göring
46:36Andrew Martin
28:36Noaa Barki
Jobs that call for the skills explored in this talk.
Rocken AG
Zürich, Switzerland
Siemens AG
Berlin, Germany
Erias Ventures, LLC
Kubernetes-clustern
Mannheim, Germany
Trinite Consulting Group Llc
Chicago, United States of America
Go
Zürich, Switzerland
D-Wave Quantum Inc.
Portland, United States of America
neuland.ai AG
Köln, Germany
