Re-logging in does not ask for username and password

[lgrossma]

On my linux VMs, when I am logged in to a cluster and I log out (both left click on connection -> log out and via command palette), after trying to log in again and choosing the last used url, I am not asked for credentials. Instead I am directly logged in again without need for a username and password.

Steps to reproduce:

1. Log in to a cluster (Fill the url, username and password. Don't save the credentials)
2. Log out
3. Log in again and choose the same url as in step 1
4. You should be asked for credentials.

Screen.Recording.2024-03-07.at.22.06.36.mov

[vrubezhny]

@lgrossma Do you know the reason of the following error?

Am I right if I tell that this is not an OpenShift cluster?

And have you updated to the latest main?

[lgrossma]

@vrubezhny I don't know why I get the error. kubectl command normally works in my terminal, so I guess the kubernetes extension does not see it in my path.

The version on which I found this bug was commit bd0747c

edit: My bad, I didn't have kubectl installed on my VM. I installed it and the errors disappeared and so did the the login/logout bug. Maybe it would be nice to add some warning that the extension might not work as expected if kubectl is not installed?

[vrubezhny]

@lgrossma KubeCtl binary is required to be installed in order to let the k8s extension API to work properly. So, as we depend on k8s extension API, VSCode Openshift Tools also requires its installation.

Does login/logout work properly once you installed the kubectl binary?

[lgrossma]

@vrubezhny Yes, it works properly. Or at least I could not replicate the issue after installing kubectl.

[vrubezhny]

Created #3975 in order to track the removing the k8s extension dependency.
We obviously need this functionality not to depend on k8s extension availability/functionality.

[vrubezhny]

@lgrossma Could you please try reproducing this issue using main branch?

After the #3987 is fixed we do not try executing kubectl anymore, so it should work properly with or without having kubectl binary installed.

[lgrossma]

@vrubezhny Tried reproducing it and the problem did not appear. Seems like it is successfully fixed!

[vrubezhny]

@vrubezhny Tried reproducing it and the problem did not appear. Seems like it is successfully fixed!

Thanks for taking care of testing it!

[vrubezhny]

Fixed with #3987