Issue

This Content is from Stack Overflow. Question asked by derek

I am using helm to deploy a namespace resource but each time helm adds annotations automatically:

meta.helm.sh/release-name=my-pr-111

which creates troubles for subsequent helm deployments using the same namespace

For example, I first deployed the namespace using command:

helm upgrade my-pr-111 ./path/helm/chart --install

Then the namespace is deployed with annotations:

meta.helm.sh/release-name=my-pr-111

Then if I do another deployment for the same namespace using command:

helm upgrade my-pr-222 ./path/helm/chart --install

Then I got an error:

Unable to continue with install: Namespace “my-space” in namespace “” exists and cannot be imported into the current release: invalid ownership metadata; annotation validation error: key “meta.helm.sh/release-name” must equal “my-pr-222”: current value is “my-pr-111”

Anyone knows how to handle this situation?

Solution

This question is not yet answered, be the first one who answer using the comment. Later the confirmed answer will be published as the solution.

This Question and Answer are collected from stackoverflow and tested by JTuto community, is licensed under the terms of CC BY-SA 2.5. - CC BY-SA 3.0. - CC BY-SA 4.0.