Kubernetes Deployment from Platform to API
summary
Claim: putting runtime manifests and infrastructure IaC in the same repository reduced deployment time from hours to minutes. Implementation uses AWS CDK or Terraform plus Kubernetes-native controllers like AWS Controllers for Kubernetes (ACK) and Crossplane to provision RDS, DynamoDB, CloudWatch and even EKS itself via compositions that abstract different implementations. A reference solution wires GitOps (Argo CD), packaging (Helm/ck8s), and controllers to reconcile PRs into provisioned infra and running application; blog posts and sample code prove the approach.
AI-written summary · about
chapters (10)
- 0:00intro
- 0:14agenda
- 1:03defining the problem statement
- 2:02application delivery streams
- 4:25platform and developer requirements
- 5:05infrastructure as code best practices
- 6:30using infrastructure controllers
- 9:29compositions in kubernetes
- 11:39practical example and solution
- 13:48summary and conclusion
related talks
39mKubernetes Deployment and Management: From Platform to API
24mKubernetes-Powered Platform Engineering: From IaC To API-Driven Infrastructure
36mMulti-Cluster Kubernetes Quick Delivery with IaC and GitOps
32mKubernetes as a Platform Framework Journey from IaC Pipelines to K8s APIs
18mAutomating Your Infrastructure Deployments on AWS
45mKubernetes Operability Tooling
35mKubernetes journey
36mKubernetes as the Universal Control Plane: From Pods to Multi-Cloud Infrastructure
