-
Notifications
You must be signed in to change notification settings - Fork 229
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
Disable refresh of Home > All Clusters on startup #2165
Comments
@illume , this is a good reason for your idea of optimizing the cluster connection in the home view. |
Would also like this to be toggle-able as I have to log into multiple OIDC for various clusters, when all I want to do usually is just access 1 or a handful (as-needed). |
I just want to add onto this. We have a lot of clusters, all require OIDC, some require a vpn, and others can only be accessed by specific people. It is extremely disruptive to have headlamp attempt to connect to all the clusters. This causes a lot of logins, spawned processes (like in the original report) and just a lot of failures. It is very disruptive. The typical workflow is an engineer wants to get to one or two clusters and look at their workload. |
I have a huge amount of clusters defined in
.kube/config
which are auto-detected on startup and refreshed by spawning background processes. Would be great if this could be disabled/optimized somehow.The text was updated successfully, but these errors were encountered: