Stefan Prodan

One more changed need, please set the status to `implementable`

@RicardoLorenzo can you please document this feature in https://github.com/fluxcd/flagger/blob/main/docs/gitbook/usage/alerting.md Thanks!

Just a friendly reminder that Helm is **not suitable** for managing the lifecycle of Kubernetes CRD controllers. CRDs have to be extracted from charts and applied on the cluster with...

@stevehipwell `skipCRDs` has no effect on upgrades as Helm ignores the `crds` dir, it only works at install time but only if the CRDs are not already applied on the...

Changing the `skipCRDs` default to `true` is not an option as HelmRelease API is at v1 and that would be a breaking change that requires a major version bump. We...

@maxisam I have no bandwidth to maintain mgob, I'm going to archive the project and link to your fork if that's Ok with you.

There is nothing missing, just that your editor doesn’t know this is a Kustomize patch that gets merged into the final object, which has all the required fields.

To properly validate the manifests please use the script included in this repo at https://github.com/fluxcd/flux2-kustomize-helm-example/blob/main/scripts/validate.sh

> The kustomization-controller could check the kustomize.toolkit.fluxcd.io/name label and if it's set and not equal to the current customization, throw an error. IMO such a thing would make Flux unusable....

If you setup Flux notifications it would be obvious what’s going on, as you’ll receive 2 notifications for the same resources from 2 different Kustomizations.