Kubernetes Deployments with Flux v2: Helm Basics
HTML-код
- Опубликовано: 20 окт 2024
- Note from May 2022: Helm support for OCI registries (like Azure Container Registry) is not experimental anymore. Please see helm.sh/docs/t... and commands like helm push and helm push. Commands like helm chart save etc... will not work with helm 3.8 or higher.
In part 5 of the series, we deploy Helm charts with Flux v2. We first deploy two Helm charts manually: a redis chart from the bitnami repository and a custom chart from the local filesystem. Next, we deploy these charts with Flux v2. The custom chart is uploaded to Azure Container Registry (ACR) and Flux v2 is configured to authenticate to ACR properly. I also illustrate the use of DependsOn to model the dependency of the app on the redis backend.
![Chino Pacas - Modo Capone (with Drake & Fuerza Regida) [Video Oficial]](http://i.ytimg.com/vi/zjv8TQ0gBkg/mqdefault.jpg)
This is really well done!!
Great series of videos, Geert!
Very interesting and helpful course for me, thanks!
Can you add in the future something with Flux v2 + flagger?
I have a video on flagger but not in combination with Flux v2. BTW flagger will be moving under the Flux CD project and GitOps Toolkit compatibility is on the roadmap. So tighter integration in short. I am not sure when but I will probably revisit flagger in the coming weeks...
Great video. I'm currently using flux this way. It's my understanding that the url in the flux helm source +""/index.yaml" needs to return an index.yaml file. Question, Is there a way to have a flux helm source point to artifacthub, which is the frontdoor/gateway for many different repositories?
As far as I understand, Artifact Hub only allows you to find charts, including the commands you need to run to install the chart like helm repo add and helm install. Once you know the repo that Artifact Hub informs you about, you can use that as the source.
Awesome series .Is there any way flux will help to rollback to previous version
Typically by modifying the YAML or reverting at the git level is what we usually do
its so difficult to find the repos which you have mentioned in all of your videos.. could have been more better if the repos were maintained properly..
It’s all in my free time and I try to do my best. These videos are old already so much of the code will not be very relevant anyway. Tnx for the tip…
This is really good. I was not able to manage the HelmRepo and HelmRelease resources in a GitHub repo to version control the changes. Also, in case helm values need to be changed, how to version control that in Github
helm chart command doesn't work
Since Helm 3.8, OCI support is not experimental anymore. Please take a look at helm.sh/docs/topics/registries/ for more information. There are now commands like helm push, helm pull, etc... Sorry for the inconvenience.
no HelmRepository objects found in flux-system namespace
Hi, it's not so easy to know exactly where this occurs. Can you provide a position in the video where the issue is? Remember the videos are already a bit older and might have issues here and there. General idea should still hold though...
@@GeertBaeke Thanks for your quick reply. its at 11:53. I did bootstrap
flux bootstrap github \
--owner=$GITHUB_USER \
--repository=helm-infra \
--branch=main \
--path=app-cluster \
--personal
than added source bitnami follwed by adding helm release for redis
flux create helmrelease redis \
--source=HelmRepository/bitname \
--chart redis \
--release-name redis \
--target-namespace default \
--interval 5m0s \
--export > helmrelease-redis.yaml
@@GeertBaeke It came up, i created the helm releases inside helm-infra instead of app-cluster. I moved it inside app-cluster and it looks good now
Thanks a lot for creating such a nice tutorial
Great that you found it. And thanks! If any other issues show up, do let me know.
Hi, can you share helm-infra?
I'm afraid I do not have that repo anymore.