Antonio Alonso Alarcon
Antonio Alonso Alarcon
Any quick comment/reaction? @stefanprodan , could this be a possible feature to add in a future?
@stefanprodan should I maybe move this better to the "discussions" section to have a debate on it?
Thanks @stefanprodan. So then, in an example based on only two Helm releases "A" and "B" (where "A" depends on "B" and we want to assure the dependency applies also...
@stefanprodan could you confirm my understanding is right .. or correct me where being wrong? (thanks a lot in advance ;-)
Thanks a lot. We can then close the issue (maybe I can do (?) ... if you tell me how I am not bothering you anymore asking to close an...
Let me work in a doc PR (for the FAQ section) to cover this (I just forked the flux2 doc repo). Posting the PR here when having it ready. Is...
If k8s kustomize supported a new option in configMapGenerator to instruct "kustomize build" to set a new .metadata.name for the generated ConfigMap object each time it is invoked, even when...
Yes, I am looking for an **automated** way (i.e. without the need for any manual "git commit" to be applied) to make the ``.spec`` of a Flux2 HelmRelease object to...
Actually I can simulate all this adding, to the k8s kustomization.yaml's configMapGenerator two files: 1. the (being there from the beginning) "values.yaml" file including the deployment specific Helm param settings...
@kingdonb you wrote above: > The design of the controller is intentional about not running up the release counter when nothing really has changed, so in the event it's needed,...