New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Startup - do not load credentials for every cluster #1889
Comments
Hello. thanks for the suggestion. Some sort of “always use this cluster” option where it defaults to the last one used? Or just default to loading the last cluster accessed perhaps? I’d like to know long it takes you on startup and what could be causing you such a long delay? I wonder how many clusters you are working with? Also I wonder how many people would like this option. For me, I’d probably prefer to load the different clusters I have. But yes, I’d like to often use the last cluster I was accessing. We can ask some more people what they think. |
Hello, I probably prefer loading the last used cluster. Cold startup takes at least 30 seconds. I have 5 Azure Kubernetes Service (AKS) clusters which one ends correctly with Bad Gateway status. Each cluster opens up command line window and then browser tab with credentials login. Next startup takes 20 seconds. AKS credentials are active for few hours and than relogin is needed. |
Do not load credentials for every cluster during Headlamp startup. If you have more than one cluster its boring and delaying your work tasks. Just load credentials for the last used cluster. Thank you.
The text was updated successfully, but these errors were encountered: