Kubernetes GitOps with Flux CD

Subscribe to show your support! goo.gl/1Ty1Q2 .
Patreon 👉🏽 / marceldempers
Today we're taking a look at a GitOps CD tool for Kubernetes called Flux.
Flux is great for keeping our cluster state in Git and it allows automated synchronization between our our Git repository and our Kubernetes cluster.
Git becomes our source of truth for our environment.
We can use Git for auditing our environment and also use feature branching to test our cluster resources against a test environment.
If you want to support the channel further, become a member 😎
marceldempers.dev/join
Checkout "That DevOps Community" too
marceldempers.dev/community
If you are new to Kubernetes, check out my getting started playlist on Kubernetes below :)
Checkout the source code below and follow along :)
Kubernetes Guide for Beginners:
---------------------------------------------------
• Kubernetes development...
Kubernetes Monitoring Guide:
-----------------------------------------------
• Kubernetes Monitoring ...
Kubernetes Secret Management Guide:
--------------------------------------------------------------
• Kubernetes Secret Mana...
Like and Subscribe for more :)
Source Code
--------------------------------------------------------------
github.com/marcel-dempers/doc...
Follow me on socials!
marceldempers.dev
Twitter | / marceldempers
GitHub | github.com/marcel-dempers
Facebook | thatdevopsguy
LinkedIn | / marceldempers
Instagram | / thatdevopsguy
Music:
Track: Joakim Karud - Fresh Start | is licensed under a Creative Commons Attribution licence (creativecommons.org/licenses/...)
Listen: / fresh-start
Track: Joakim Karud - That Day | is licensed under a Creative Commons Attribution licence (creativecommons.org/licenses/...)
Listen: / that-day
Track: Joakim Karud - Holiday Blues | is licensed under a Creative Commons Attribution licence (creativecommons.org/licenses/...)
Listen: / holiday-blues
Track: Joakim Karud - If I Could I'd... | is licensed under a Creative Commons Attribution licence (creativecommons.org/licenses/...)
Listen: / if-i-could-id
Track: souKo - souKo - Parallel | is licensed under a Creative Commons Attribution licence (creativecommons.org/licenses/...)
Listen: / parallel

[@MarcelDempers]

My Series on CI/CD 👉🏽kzbin.info/aero/PLHq1uqvAteVsSsrnZimHEf7NJ1MlRhQUj

[@mingli9563]

This is the first channel that has a car-review style tech videos. Awesome!!

[@SacrificialGoat94]

Epic quality. Concise. Informational. Thanks. Keep them coming!

[@kunduvikram]

Short and explained mostly used features of Flux. Nicely Done!! 👏👏

[@devopskey6251]

You are one of my favorite instructor and every time you deliver new technology with 100%. 😘❤💯👏

[@trickytibo]

A big thank you for your video and your teaching skills. Always so enlightening.

[@developer-guy]

another great video from Marcel , thanks a lot !

[@farrukhahmedsid]

Nicely explained Flux in short time.. Very much useful. Thanks...

[@martinmolinaalvarez9801]

Exactly the kind of video I was looking for!

[@lukejkw]

Lekker channel boet. Good to see a saffa making great tech content

[@developer-guy]

nice, it was a great getting started video for flux !

[@jasonsinclair2968]

Good Work! cleary explained at a good pase with no BS

[@christianibiri]

Great video Marcel!

[@yasirtariq4616]

Great demo. I loved it

[@TheMrFert]

Like the narrator style. Finally different accent rather than majority KZbin IT channels

[@Diolev377]

Great video helped me a lot, Thanks.

[@couscousburify]

Thank you for the video bro !

[@MatiFix]

Thanks ! Great video!! Well explained!

[@ridmapabasara2714]

dude thank you for doing this.

[@esoterictech]

I don't comment on videos often but damn this was good! Thanks a lot for the detailed explanation!

[@aietisreekar2425]

this was an awesome clip

[@arpanchakraborty9874]

Fantastic, thanks a lot!!

[@avishayg1986]

Thank you kind sir!

[@fxxxxxxxxxxf]

Nice video and a channel! Thanks

[@mamun001]

Thank you!

[@herrownice]

Great Video !!!

[@mingli9563]

Great Job

[@gadieichhorn7570]

thank you, very nice, how would you manage secrets like DB connections with Flux?

[@msoranno]

great video Marcel. Flux is a great tool to help in a very specific situation, but as far as i can see does not fit well in a large scale K8s clusters with large teams working on several components to be deployed. Currently we are using tekton btw.

[@forexmeter3900]

Very well explained. Since your video is 2 years old, can you do another video and demo the most recent capabilities of Flux? Thank you!

[@dylans5233]

Good job mate! Just wondering if you could cover a flux tutorial for a multi-tenancy cluster? Thanks

[@jayeshthamke7860]

That's great! Does Flux support pulling images depending on tags like -dev or -release/ -stable ? Thanks

[@vengamnaidu9273]

hi Marcel , can you make detailed videos on flux working with helm, rancher and other things like add your own key in github and flux. how to maintain different repository source of truth with flux. Heart-full thanks for sharing your knowledge.

[@Narco_89]

Amazing! Very well explained in few minutes! I would see the entire pipeline with flax, like: 1. the dev which push new code on git 2. Travis tests it on another cluster (maybe flax is listening all non-master branches too and deploy on same cluster but another workspace?) 3. a git owner accept the PR 4. flax deploy the changes made only on master Hope this is not just a unnecessary repetition. Thank a lot for this video!

[@CienciaFiccionPeru]

Flux

[@oy_oy]

Thanks for this explanatory video. I have some doubts: - does Flux CD validate your manifests to find missing items? - does it allow to reuse manifests with templates with parameters? - Also, let's say we share a NLB id within Service annotations among hundreds of applications, does it mean we will have to run the pipeline in all of them? With Helm you can update all your Ingresses and objects in your cluster in a single shot and sort previous questions, as well as handling all the objects as a single versioned package

[@cschelin]

Currently I'm maintaining my configurations via ansible playbooks. The issue I can see with Flux is with credentials or other similar items that need to be secure. We have connect strings to databases (for example) which has a password. We also have some configurations with SSL certificates including the private key. Right now I have such things in an Ansible Vault and when I need to update that yaml, I run the ansible playbook which creates the necessary yaml to be applied. For a git pull, how would that be addressed using flux?

[@NiteshKumar-do4en]

Yeah I need this flux please Argo CI for more knowledge of workflows

[@renus1195]

if possible make a video on HELM OPERATOR AND FLAGGER and about custom resource definition (helmrelease) please

[@koodauskanava9096]

Can you do a video about flux2? Use simple helm release. Thanks!

[@singyongjoong56]

Which namespace will the sync-ed workloads be deployed in?

[@davidgg8462]

very good

[@chongerwin]

Thanks!

[@MarcelDempers]

Thanks so much for the support 💪🏽🍻

[@softwareengineer5764]

Hi Marcel. You are fantastic teacher. I really request you to make a video for flux V2. Is it possible to follow this video with flux V2 ??

[@renus1195]

please make a video on flux helmoperator and flagger component

[@chandup]

Question, If I want to use flux with ansible or Chef, is it possible for non k8s workloads?

[@akshaysood1569]

Awesome

[@dqfold5557]

Awesome Videos! So much good information in such a short time, it's excellent! I have a beginner question. What does the daily work of a devops look like? I feel like it takes months to learn how to master all these tools (AWS, K8S, FLUX, Jenkins, Argo, Promotheus, Grafana, ...) and once that was done, we quickly set up a cluster, the CD / CI, etc (well, it seems fast for you). But when done, it more or less works on its own. Once we have set up the clusters, CI/CD of the different projects that a company is working on, what is the job of the devops guy?

[@MarcelDempers]

Thank you 💪🏽🤓 The idea is that the platform works on its own and does not require constant daily tasks. Kubernetes helps with the tedious tasks, such as setting up load balancing, hooking up logging\monitoring, health checks, auto restarts etc, so a devops engineer can focus on more important tasks. As a DevOps engineer you should strive to automate yourself out of a job. Build systems and platforms that do things for you and others so you can do more important work. There will always be more important things to do. Don't become a gatekeeper for developers. Help developers become self sufficient. Help build tools that empower developers to code, build, test and run applications in production in minutes, rather than days. Give them tools to deploy 100s of deployments per day. You can build tools and services that give developers and team freedom to work fast within boundaries. Give them capability to log, monitor and observe their systems in production with a click of a button. Do all the above with security and best practises in mind. Although these systems will work and function on their own, you will always have things going on and have room for improvement. For example: How do you upgrade your platforms with 0 downtime and 0 disturbance to CI/CD and team operations? How do you keep monitoring and ingress controllers up to date? How do you improve container image security and provide up to date patching? ..the list never ends :)

[@dqfold5557]

@@MarcelDempers Thank you for taking the time to respond and for this good explanation!

[@Santiago-yy3jg]

are "Automations, locks and annotations" still available with the newest version of Flux? Thanks for your videos.

[@ghauri001]

Marcel what do you like most feature/technology wise? Flux or Argo?

[@robertkerr229]

Hey boss, on Windows, use Rapid Environment Editor rather than control panel for environment variable editing. Be sure to run as administrator.

[@hugomartinez1020]

Hi Marcel, nice video on Flux, great job! Just wondering how I can solve this issue I am having right now: flux pod is crashing, due to this reason: cannot patch resource \"secrets\" in API group \"\" in the namespace \"flux\"" Any hint on this? Just researching to apply it in my current project, please help me as we want to make it more modern :) Thanks in advance!

[@K2ThaYo]

Helm charts all the way... You can lint it, dry run and even automatically rollback with the atomic flag

[@isaacyuen5409]

Hi You said we can update the git branch flux is keeping watching into for testing purposes before we merge it back to master. How can that be done with fluxctl? What are the commands? Thank you for your videos. They are very informative!

[@MarcelDempers]

Thank you! 💪🏽 The fluxctl install command takes in a branch name for a git repository docs.fluxcd.io/en/1.18.0/references/fluxctl.html#using-fluxctl-install

[@aritchakraborty9543]

Suppose I am having 5 Microservice and in the git-path do I need to mention 5 repo name explicitly??

[@gregoryhammond9341]

I'll most certainly try this later however I have one concern: Why does the flux auth-key need write permissions to the Repo it's suppose to be pulling from? EDIT: Should have waited till the end. Sorry.

[@amine250]

I prefer ArgoCD :)

[@kojitechs]

i love flux

[@webmakaka]

*Молодец!*

[@chandup]

Hi Nice video. How to contact you? Do you have a slack channel or anything else?

[@jerilcj2523]

Is there any option to run bash script in Flux CD? I have got a few *.yaml files and a bash script which has be executed as well.

[@MarcelDempers]

You could run a pod, perhaps as a job and have it run once off. The pod can run any arbitrary OS and place your bash in a configmap, mount it to the pod, and execute it at start up using the entrypoint.

[@jerilcj2523]

@@MarcelDempers So like you said I created a another pod which is of kind:job and included the script.sh. So now I have two pods 1. mongodb pod 2. job pod which has (script.sh) In the script.sh file, I run "kubectl exec" to the main pod (mongodb pod) to run few commands The script gets executed, but I get the error "cannot create resource "pods/exec in API group" So I created a clusterrole with resources: ["pods/exec"] and bind it to the default service account using ClusterRoleBinding ``` kind: ClusterRole apiVersion: rbac.authorization.k8s.io/v1 metadata: name: pod-reader rules: - apiGroups: [""] resources: ["pods", "pods/log"] verbs: ["get", "list"] - apiGroups: [""] resources: ["pods/exec"] verbs: ["create"] --- kind: ClusterRoleBinding apiVersion: rbac.authorization.k8s.io/v1 metadata: name: service-account-role-binding namespace: default subjects: - kind: ServiceAccount name: default namespace: default roleRef: kind: ClusterRole name: pod-reader apiGroup: rbac.authorization.k8s.io --- apiVersion: v1 kind: ServiceAccount metadata: name: default namespace: default In the pod which is of kind:job, I include the service account like shown below restartPolicy: Never serviceAccountName: default but I still get the same error. What am I doing wrong here ?

[@jerilcj2523]

Thanks..I got it working..

[@sebastiansmuzynski5508]

Why does Flux require write permissions to read code?

[@vikrammaiya003]

Flux will update the tag of image when new images are pushed to image registry

[@mab2278]

Really nice tutorials but please don't play music in the background. I have no idea where comes such a strange idea.