To change your active cluster, you don't need to re-enter API keys, re-download certs, or pray to the cloud gods. You just run:
You’ve just been bitten by the .
kubectl config use-context <context-name> For example: kubectl change context
We’ve all been there. And the single most important command to break that curse is: kubectl config use-context . By default, kubectl doesn't care about your feelings—or your environment. It remembers the last cluster you touched. If you were troubleshooting in dev-east yesterday, you’re likely still pointing at dev-east today. To change your active cluster, you don't need
The kubectl Context Shuffle: How to Stop Breaking Production (and Your Sanity) To change your active cluster