docs(install): clarify the --replace flag

[remcohaszing]

The description of the --replace flag was unclear, as it can’t be used to replace active releases.

I thought this was a bug, but the current behaviour works as expected according to some discussions in #6122.

Signed-off-by: Remco Haszing remcohaszing@gmail.com

[hickeyma]

@remcohaszing Thanks for pushing this clarification. I have a suggestion on the text.

[towolf]

For real, we were not using helm install before, due to tiller, and now want to "adopt" the existing k8s resources when they come wrapped in a helm 3 release.

So, why does helm install --replace not overwrite the existing resources, when they are found in the cluster? Why is that the expected behaviour? @bacongobbler

[hickeyma]

@remcohaszing Do you mind signing the dco: https://helm.sh/blog/helm-dco/#what-if-i-forget-to-sign-off-on-a-commit

[remcohaszing]

@remcohaszing Do you mind signing the dco: https://helm.sh/blog/helm-dco/#what-if-i-forget-to-sign-off-on-a-commit

Oops, amended 😅

[hickeyma]

LGTM, thanks @remcohaszing

[hickeyma]

Going to hold off on merging as waiting on response to question asked in #7089 (comment)

[towolf]

Going to hold off on merging as waiting on response to question asked in #7089 (comment)

Thanks, I'd really love to know why it's refusing to replace the resources.

I think install --replace or maybe install --replace --force should say "these names are mine now, going to replace them".

[remcohaszing]

I also need the feature mentioned in #7089 (comment). This is why I ran into this in the first place.

I created #7103 as a feature request to support this.

[hickeyma]

@towolf Going to merge as this PR related to updating the help doc to the current implementation. Do you mind re-asking your question from #7089 (comment) in #7103 ?