-
Notifications
You must be signed in to change notification settings - Fork 364
Description
maybe this not a problem for kube-ps1,but i think it's a limitation you must known when you begin to use kube-ps1.
how i find it?
I have four kubernetes clusters.i installed kube-ps1 on one of the cluster's master node.
I use jumpserver to login into the node.There is a namespace created on two clusters.I check the namespace on cluster1to ensure there is no pods inside the namespace,then i copy the ssh session,and switch another cluster to check pods running under the namespace.After this i went back to the previous ssh session,the shell prompt shows i'm in cluster 1,so i delete the namespace,after the command execute complete,the kube-ps1 switched to cluster 2.Oh my god,i remove namespace on the wrong cluster.so you must be careful when you use kube-ps1 on the production environment.