GitLab + Flux!
summary
GitLab integrates Flux as its recommended GitOps engine and wires Flux into the GitLab Agent for Kubernetes so clusters keep a bi-directional connection while Flux handles reconciliation. Key deliverables: OCI image support (container registry changes recently fixed), pipeline integration that surfaces Flux as a pipeline job, and agent-managed tokens to avoid creating five tokens per repo. Experimental OCI + pipeline features land May 22, a beta with automatic Flux updates and UI visualization targets roughly one month after that.
AI-written summary · about
chapters (6)
- 0:00GitLab + Flux intro
- 3:10Why GitLab chose Flux
- 7:01Pipeline integration with Flux
- 10:11Simplifying Flux setup
- 11:14Release timeline & features
- 12:19Q&A on OCI & security
related talks
26mGitOps Lifecycle Management
33mFlux Maturity, Feature, and Contrib Update
39mEnhance Your Kubernetes Experience with GitOps & Flux
21mIntroduction to FluxCD
26mEmpowering SRE with GitOps
06mFrom Policy to Production: Flux and GitOps as Governance Control...
33mGitOps with Flux and OCI Registries
33mMay the Flux Be With You: Tales From the GitOps Trenches
