Efficient GitOps with GitLab and Flux

In this video, I am covering everything from the basics of GitOps to advanced integrations with GitLab and Flux.
🕒 Jump to Sections:
01:32 GitOps Basics
04:45 Architecture - The GitLab Agent and Flux
05:50 Demo - Bootstrapping Flux for GitLab
07:50 Deploy the GitLab Agent for Kubernetes with GitOps (Flux)
10:30 Demo application deployment with GitOps
13:05 The GitLab Kubernetes Dashboard
🔗 Useful Links:
Token Management: gitlab.com/gitlab-com/Product...
Pipeline Integration: gitlab.com/gitlab-org/gitlab/...
gitlab.com/groups/gitlab-org/...
gitlab.com/gitlab-org/gitlab/...
#GitOps #GitLab #FluxCD #DevOps #Kubernetes #CI/CD #TechTutorial #GitLabTutorial #CloudComputing #SoftwareDevelopment

[@anudeepchalluru7598]

Just what I was looking for since yesterday 😃😃

[@alexanderdess303]

Thanks - happy to hear this and hopefully it helped :)

[@user-pe6it3xv5m]

Could you share information about how to configure agentk in case Flux? On GitLab website seems there is a bit outdated info about GitOps worflow with applying manifest via kubectl directly. Please correct me if I'm wrong

[@GitLabUnfiltered]

There are multiple ways how to deploy the agent. One is the imperative way which you found in the documentation. For GitOps with Flux we recommend to store the helmrelease in the declarative way. This is the Link to the documentation on how to do this with flux: docs.gitlab.com/ee/user/clusters/agent/gitops/flux_tutorial.html#install-agentk

[@user-pe6it3xv5m]

Is it possible to confirm in a pipeline that a change which was made via flux was successfull? I want to be confident that helmrelease and reconcilation have apllied successfully

[@GitLabUnfiltered]

Hi, this is a great question and this is what we are working against. You can follow the issue for more details: gitlab.com/gitlab-org/gitlab/-/issues/405007