Cannot install istio-operator in existing namespace

[vhosakot]

Bug description

Cannot install istio-operator in existing namespace using helm. Using istio 1.6.8.

[x] Installation
[x] User Experience

Expected behavior

Istio-operator should be installed in existing namespace instead of newly created namespace.

Steps to reproduce the bug

Used helm to install https://github.com/istio/istio/tree/1.6.8/manifests/charts/istio-operator.

git clone https://github.com/istio/istio.git
cd istio
git checkout 1.6.8

$ kubectl get ns my-ns
NAME     STATUS   AGE
my-ns    Active   22h

$ helm install my-ns-istio-operator manifests/charts/istio-operator --set operatorNamespace=my-ns
Error: rendered manifests contain a resource that already exists. Unable to continue with install: Namespace "my-ns" in namespace "" exists and cannot be imported into the current release: invalid ownership metadata; label validation error: missing key "app.kubernetes.io/managed-by": must be set to "Helm"; annotation validation error: missing key "meta.helm.sh/release-name": must be set to "my-ns-istio-operator"; annotation validation error: missing key "meta.helm.sh/release-namespace": must be set to "default"

Using istioctl does not work either and istio-operator was installed in the newly created istio-operator namespace instead of existing namespace.

$ ./istio-1.6.8/bin/istioctl operator init --namespace my-ns
Using operator Deployment image: docker.io/istio/operator:1.6.8
✔ Istio operator installed                                                                                                 
✔ Installation complete

$ kubectl get pods -A | grep istio
istio-operator   istio-operator-b87f5fdb5-mqcft      1/1     Running   0          101s

$ kubectl get ns my-ns
NAME              STATUS   AGE
my-ns             Active   22h
istio-operator    Active   100s

Version (include the output of istioctl version --remote and kubectl version and helm version if you used Helm)

$ ./istio-1.6.8/bin/istioctl version --remote
no running Istio pods in "istio-system"
1.6.8

$ kubectl version
Client Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.6", GitCommit:"d32e40e20d167e103faf894261614c5b45c44198", GitTreeState:"clean", BuildDate:"2020-05-20T13:16:24Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.6", GitCommit:"d32e40e20d167e103faf894261614c5b45c44198", GitTreeState:"clean", BuildDate:"2020-05-20T13:08:34Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/amd64"}

$ helm version
version.BuildInfo{Version:"v3.2.4", GitCommit:"0ad800ef43d3b826f31a5ad8dfbb4fe05d143688", GitTreeState:"clean", GoVersion:"go1.13.12"}

How was Istio installed?

Istio-operator was installed using helm, see steps under "Steps to reproduce the bug".

Environment where bug was observed (cloud vendor, OS, etc)

Kubernetes v1.17.6 installed using kubeadm in Ubuntu 18.04.4 (Bionic Beaver).

[pisto]

Please just remove the Namespace resource from the chart. Creating a namespace with Helm is not supported (helm/helm#3503).

[istio-policy-bot]

🚧 This issue or pull request has been closed due to not having had activity from an Istio team member since 2020-08-13. If you feel this issue or pull request deserves attention, please reopen the issue. Please see this wiki page for more information. Thank you for your contributions.

Created by the issue and PR lifecycle manager.