traefik-crds is using unexpected meta.helm.sh/release-namespace annotation

[shinebayar-g]

Welcome!

• Yes, I've searched similar issues on GitHub and didn't find any.
• Yes, I've searched similar issues on the Traefik community forum and didn't find any.

What version of the Traefik's Helm Chart are you using?

1.2.0

What version of Traefik are you using?

3.3.2

What did you expect to happen ?

CustomResourceDefinition without meta.helm.sh/release-namespace annotation since they're global resources.

What did you notice instead ?

I'm using traefik-crds to deploy CRDs separately. However, it seems, CustomResourceDefinition output file is containing meta.helm.sh/release-namespace annotation which seems unnecessary. On top of that, the value is using $scope.Release.Namespace which defaults to the current kube config namespace which leads to inconsistent output.

What are your values ?

No values.

Additional Information

[mloiseleur]

Hello @shinebayar-g ,

Thanks for this detailed issue.
As far as I remember, it's required for helm to handle those resources.
It's consistent: it's the the name and the namespace of the helm release that is handling that global resource.

Feel free to open a PR if you need to remove them and you think you have found a way to handle those resources with helm without those annotations.

[shinebayar-g]

As far as I remember, it's required for helm to handle those resources.

Where did you get that information? kube-prometheus-stack-crds chart doesn't use it. In fact, I don't recall this annotation being used.

It's consistent: it's the the name and the namespace of the helm release that is handling that global resource.

No it's not consistent. If --namespace flag is not supplied by user, it looks up kube config and use whatever namespace is set. So it's not idempotent.

I created a PR here #1338