Replies: 1 comment 1 reply
-
Thank you so much @onedr0p for bringing this topic up. We discussed about this a couple months ago and I think it's a good idea to bring it up again. I am personally feeling that it's a bit hard to troubleshoot problems for users too with the current chart versioning. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi 👋🏼
It would be great for automation purposes if the version of the chart matched the version of the application. I deployed the helm chart with
installCRDs: false
. I am installing CRDs via aGitRepository
and aFluxtomization
so the helm chart and crds versions can be managed by Renovate.The reason for doing this is so I can contain the HelmRelease and Terraform CRs in the same
Fluxtomization
.In simplest terms if you try to apply the following Kustomization for the first time it will fail because the CRDs are not installed yet and I want a automated way to manage versions of the CRDs and Helm Chart in a single
Fluxtomization
.An full example can be seen here with Kyverno:
Kyverno GitRepository and the Fluxtomization applying their CRDs.
The apps
Fluxtomization
which under it has Kyverno CRs and the KyvernoHelmRelease
.The Kyverno
HelmRelease
and the CRs which are all under the same appsFluxtomization
The pull request where you can see the versions being updated on a new release.
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions