Is stand alone mode really going away?

[michaelajr]

Describe the question

We set up the kube config with kubelogin in standalone mode, and then explicitly call kubelogin to set oidc credentials. We do this because we run kubectl from inside a container and mount the kube config. This all works well for us and it is the only way we can use kubelogin (can't pop the browser from inside a container).

My questions is, is stand alone mode really going away? If not, we would really like a way to turn off the warning message - or just get rid of it all together since stand alone is a valid use case.

[int128]

Thank you for your suggestion. I thought the credential plugin mode is enough for most cases, but I decided to keep the standalone mode. I will remove the warning message.