Destroyed and re-created the istio-system environment, and then any pod in other namespaces I deleted would not come back. I could also not launch any new pods. See below.
I restarted kube-apiserver, and after a few seconds my pods relaunched.
So this will bring down my entire cluster if I wanted to change the config. Maybe a better alternatie would be to apply the new config and then just destroy all pods running in istio-system??
Bug:
What Version of Istio and Kubernetes are you using, where did you get Istio from, Installation details
Is Istio Auth enabled or not ? NO
Did you install the stable istio.yaml, istio-auth.yaml.... or if using the Helm chart please provide full command line input.
helm template install/kubernetes/helm/istio --name istio --namespace istio-system > $HOME/istio.yaml
What happened:
Destroyed and re-created the istio-system environment, and then any pod in other namespaces I deleted would not come back. I could also not launch any new pods. See below.
What you expected to happen:
1) Install istio. helm template install/kubernetes/helm/istio --name istio --namespace istio-system | kubectl create -f -
Works fine. But wanted to reinstall with new optios
2) helm template install/kubernetes/helm/istio --name istio --namespace istio-system | kubectl delete -f -
3) helm template install/kubernetes/helm/istio --name istio --namespace istio-system --set global.proxy.includeIPRanges="10.2.0.0/16\,10.0.0.0/16" | kubectl apply -f -
4) delete my pods in my test namespace.
The pods will not relaunch.
I restarted kube-apiserver, and after a few seconds my pods relaunched.
So this will bring down my entire cluster if I wanted to change the config. Maybe a better alternatie would be to apply the new config and then just destroy all pods running in istio-system??
Thanks!