From Toil to Empowerment: Building Self-Service Ingress with...
summary
Claims a GitOps pipeline that turns fragmented, manual ingress (load balancers, TLS, DNS, edge rules) into zero-touch ingress provisioning across many clusters by converting external services into Kubernetes resources and operators. Uses cert-manager and external-dns where possible, and a custom zone provisioning controller plus a custom edge/config operator to allocate DNS zones, create records, push firewall/edge config and emit metrics. Reconciles changes in minutes, adds integration tests, auditable YAML, and improved observability.
AI-written summary · about
chapters (8)
- 0:00Self-service ingress intro
- 1:00Ingress management importance
- 3:17Fragmented ingress model
- 6:54Developer experience challenges
- 8:57Kubernetes-native ingress solution
- 11:52Operator-driven ingress components
- 13:20Developer and platform outcomes
- 15:29Summary
related talks
38mGitOps for Istio - Manage Istio Config like Code
16mWant to extend GitOps to Infrastructure and Workloads? Here's how.
33mKubernetes As A Service with GitOps
30mOur Journey in Integrating GitOps Tools Into Delivery Pipelines
35mApproach to GitOps — Achievements, Mistakes and Lessons Learned
47mGitOps - Using Git as your source of truth for build, deploy and observability
43mConfiguration as Data, GitOps and Multi Cluster The Key to Successful Servic
27mGitOps Your Gateway: Automating Traffic Management at...