Ok. so it’s been awhile since my last post and I just notice I have alot of stuff in my draft. Anyway, here’s a quick post on how to solve Supervisor Namespace not showing up in kubectl CLI when trying to login to TKGS.
The issue:
if you use kubectl vsphere login in a machine that already has kubeconfig configured, changing context won’t work
I’ve been doing alot of kubernetes and have collected a few kubeconfig. This is causing the kubectl-vsphere to not show the supervisor namespace.
Workaround
Set KUBECONFIG enivronment variable to none before logging in with kubectl vsphere login to have the CLI set the supervisor namespaces available for that session.
export KUBECONFIG=""
Hope that helps!
