This is a known issue affecting Tanzu Mission Control. There is currently no resolution.
Workaround:
Use the following steps to workaround this issue:
- On the system where you will run kubectl commands, issue the following command:
export TMC_BROWSER=none
- Download the provided <cluster-name>.yml file to the system where you will run kubectl commands.
- Issue the provided kubectl --kubeconfig=<path/to>/kubeconfig-test-<cluster-name>.yml get namespaces command.
- Copy the provided link from the output of Step 3 and paste in to the URL bar in a browser on a different system where a web browser is available.
Note: If you are not already logged in to cloud.vmware.com, you will be presented with a login screen. Enter your credentials. After you login, or if you were already logged in, you will see a page displaying the following text:
tmc login flow complete
You are authenticated and can close this page.
Your kubectl command should complete and you will see a list of namespaces in the cluster.
Note: An alternative workaround would be to run the provided kubectl command from a system with a web browser installed and after the authentication is successful, copy the .vmware-cna-saas folder from the user's home directory to the system where you will normally run kubectl commands. The authentication token in this folder will be active for 90 days.