Supercharge your Kubernetes deployments with Flux v2 and GitHub - Introduction
HTML-код
- Опубликовано: 20 окт 2024
- This is part 1 in a series where we take a look at Flux v2 and the use of GitOps principles to deploy to Kubernetes. We first discuss the tools and then proceed with the first steps: installing the CLI and bootstrapping the cluster.
In part 2, we will look at deploying an application in different environments with kustomize and how to add monitoring and alerting.
#gitops #kubernetes #flux
I am Simply Overwhelmed after Looking into these Videos . Though i was reading the Flux documentation It was hard to understand the use Cases . Things are really getting clear now
I would Love to connect with you and gain More /Complete Insight of the Future with GITOPS . Thank you again for these Videos.
Thanks for this excellent video about Flux introduction. Very well structured and nicely explained.
My guy, you're fantastic. Very clear and precise !
Thanks for this really nice explanation of flux v2. Looking forward to see the next parts of this series!
Thanks for your excellent video! First my bootstrap failed with a timeout, but adding --timeout=20m helped!
Nice, clear explaination.
What is the difference between flux v2 and flux2 ? . Can you please show how to install Flux2 via Helm install. Thank you.
Question: I see that flux bootstrap command deploys flux for us. So, how to we manage the upgrade of flux if there is new release?
And can we club multiple k8s clusters in one flux deployment?
If you have used bootstrap, you can update the flux CLI and then run flux bootstrap again like you did before. That will update the manifests in /flux-system/gotk-components.yaml. As per the multiple k8s clusters, you can have a folder per cluster in your repo but you install flux for each cluster. So in essence, flux bootstrap per cluster but use the different folders.
@@GeertBaeke Thank you for responding. It's helpful. One another question is regarding the scalability. Is there even a question for scalability of flux as I could see it deploys only controllers with 1 replicas. Will there be any case when we might need more replicas??
@@manmohan1391 That would all depend on the rate of change in manifests and Helm charts + the intervals you set. We have only deployed Flux in clusters with 10-20 nodes where this cannot be an issue. I think the recommendation is to leave them at 1.