Great video, there are a lot of GitOps tools there currently I'm using Argocd because have niceful GUI and also easy to monitoring the deployment. Hoping you make some videos regarding security such as neuvector
Great and compact video. I've learned a lot. But what's next, the app is deployed, how my CD pipeline know about the finished GitOps deployment and go on with further steps?
With flux, your CI system only needs access to GIT and not to your K8s clusters. You could have distributed platforms in different regions and different dev\staging\uat\prod environments and no need to stitch up your CI system to all these environments. Flux helps here as it syncs environments with GIT
@@MarcelDempers I see, thank you for taking the time to respond. In our case the CI is already configured to do everything everywhere so it feels easier to replace the current deployment job with a kubectl apply. But it's our case.
great! Is one Flux/Kustomize installation enough to manage all deployments in the cluster across namespaces? Does that require an RBAC 'cluster-admin' role?
Hi, I used the flux bootstrape command in which I specified the repo URL and other information, then the command automatically created `flux-system` folder in my repo under which it automatically pushed the Flux manifests, the syncing between my repo and the cluster is then working out of the box. So, I wonder in your video why you suggest to have `gitrepository.yaml`? I mean isn't everything needed for syncing are already generated under `flux-system` folder by flux command?
I believe Argo has a larger ecosystem and more features since it is a lot older than Flux and more popular too. It has a UI as well which makes it more attractive to people and improves uptake
@@MarcelDempers Right, I've used ArgoCD and like it. And besides CD, it has RollOuts and Workflows to supplement the CD. Which is why I'm curious to know what FluxCD has that Argo doesn't as I've never used Flux before.
Thanks for the detailed video., I have few queries and if possible provide me some input which will help 1. What will be the best create and manage multiple environment Manifest file while using Flux 2. How can we execute dry-run (terrafrom-plan) before deploying kubernetes manifest file which will avoid wrongly deploying configuration to environment like Prod
I have deployed flux bootstrap in my project but when I have multiple images in ghcr how to deploy if any changes to images or deployments? Should I update image policy will all the details ?I'm lost completely when you explained example.2 app using yaml files...can anyone comment here how to fix it?
Can I bootstrap flux for multiple git repos at the same time? Or can I have multiple --path attributes for single git repo while bootstrapping flux. Can someone help me with this?
Now this is a real content, Thanks for creating such gold content Marcel!
Marcel is back! 😀 Awesome and insightful as ever!
The best tech youtuber ever! period! Welcome back!
Good to see you back
Welcome back! 💪
What an amazing explanation of Flux, thanks!!
Marcel - Your content is wonderful. Thank you!
Excelente conteúdo. Que bom que voltou a fazer vídeos!
The King is back!
Great video, there are a lot of GitOps tools there currently I'm using Argocd because have niceful GUI and also easy to monitoring the deployment. Hoping you make some videos regarding security such as neuvector
You are DEVOPS Monster !
Was waiting for you releasing the next parts of how to run postgresql on kubernetes 😳
its coming 💪🏽🙏🏽
Where have you been? hope you doing well, love your videos!
16:40 Built that docker IMAGE 👍
The author is the real deal🎉
Do you suggest using flux for production critical K8 clusters ?
Very good video!
Woop woop you're back!
Great video, tz so much! But why do we have flux if we still have to kubectl create our stuff?
Great and compact video. I've learned a lot.
But what's next, the app is deployed, how my CD pipeline know about the finished GitOps deployment and go on with further steps?
if the CI job should update the image tag in the yaml anyway, what's the use of flux. One more line and it's applied to k8s.
With flux, your CI system only needs access to GIT and not to your K8s clusters. You could have distributed platforms in different regions and different dev\staging\uat\prod environments and no need to stitch up your CI system to all these environments.
Flux helps here as it syncs environments with GIT
@@MarcelDempers I see, thank you for taking the time to respond. In our case the CI is already configured to do everything everywhere so it feels easier to replace the current deployment job with a kubectl apply. But it's our case.
marcel, I have been waiting your new video release.
Whatever the content, I am here because of the forearm thumbnail.
great! Is one Flux/Kustomize installation enough to manage all deployments in the cluster across namespaces? Does that require an RBAC 'cluster-admin' role?
I can see there are RBAC settings in the flux bootstrap directory once you bootstrap it against a git repo. There are cluster roles
Missed ya!
Hi, I used the flux bootstrape command in which I specified the repo URL and other information, then the command automatically created `flux-system` folder in my repo under which it automatically pushed the Flux manifests, the syncing between my repo and the cluster is then working out of the box. So, I wonder in your video why you suggest to have `gitrepository.yaml`? I mean isn't everything needed for syncing are already generated under `flux-system` folder by flux command?
he's back!
What does FluxCD have over ArgoCD?
I believe Argo has a larger ecosystem and more features since it is a lot older than Flux and more popular too.
It has a UI as well which makes it more attractive to people and improves uptake
@@MarcelDempers Right, I've used ArgoCD and like it. And besides CD, it has RollOuts and Workflows to supplement the CD. Which is why I'm curious to know what FluxCD has that Argo doesn't as I've never used Flux before.
What sells to me from Flux is you can leverage Helm atomic upgrades with automatic rollback. ArgoCD doesn't have automatic rollback/remediation.
Thanks for the detailed video., I have few queries and if possible provide me some input which will help 1. What will be the best create and manage multiple environment Manifest file while using Flux 2. How can we execute dry-run (terrafrom-plan) before deploying kubernetes manifest file which will avoid wrongly deploying configuration to environment like Prod
Welcome back
I have deployed flux bootstrap in my project but when I have multiple images in ghcr how to deploy if any changes to images or deployments? Should I update image policy will all the details ?I'm lost completely when you explained example.2 app using yaml files...can anyone comment here how to fix it?
Can I bootstrap flux for multiple git repos at the same time? Or can I have multiple --path attributes for single git repo while bootstrapping flux. Can someone help me with this?
Привет, товарищ!
So cooooool!
at last!!!
Its been awhile