Managing Software Upgrades with a kpt, GitLab and Flux Workflow in a Telecom Context
summary
Proof-of-concept uses kpt + GitLab CI to run kpt package update and create merge requests that show a real 3-way diff for Flux-managed Helm deployments; a live demo increments a Helm chart and Flux reconciles after MR approval. Works reliably for KRM-formatted manifests but fails for values.yaml and needs a container runtime, public gcr pulls and lacks git/registry auth, making it impractical for many air-gapped environments and regulated telco sites. Overall: promising for bundled Helm updates but not production-ready for strict telco constraints (no registry auth).
AI-written summary · about
chapters (6)
- 0:00Start
- 1:09Software delivery in telecom
- 3:19High-level architecture
- 6:42PoC setup
- 13:38Learnings (1/2)
- 17:07Summary
related talks
29mAccelerating GitOps Adoption with Flux
47mDevOps:Config Mgmt for Kubernetes workloads with GitOps and Helm
37mHelm Users! What Flux 2 Can Do For You
39mEnhance Your Kubernetes Experience with GitOps & Flux
26mGitOps Lifecycle Management
38mAutomated & Observable Deployments with Flux + Keptn
22mPush to Prod: GitOps Workflows on k8s with FluxCD
33mFlux Maturity, Feature, and Contrib Update
