You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 16, 2019. It is now read-only.
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??
Thanks!
The text was updated successfully, but these errors were encountered:
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:
helm template install/kubernetes/helm/istio --name istio --namespace istio-system | kubectl create -f -
Works fine. But wanted to reinstall with new optios
helm template install/kubernetes/helm/istio --name istio --namespace istio-system | kubectl delete -f -
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 -
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!
The text was updated successfully, but these errors were encountered: