Skip to content
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

Open
visit1985 opened this issue Jul 16, 2024 · 3 comments
Open

Disable refresh of Home > All Clusters on startup #2165

visit1985 opened this issue Jul 16, 2024 · 3 comments
Labels
blocker Completely prevents the user from using the software. enhancement New feature or request frontend Issues related to the frontend

Comments

@visit1985
Copy link

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.

image

@joaquimrocha
Copy link
Collaborator

@illume , this is a good reason for your idea of optimizing the cluster connection in the home view.

@joaquimrocha joaquimrocha added enhancement New feature or request blocker Completely prevents the user from using the software. frontend Issues related to the frontend labels Jul 16, 2024
@joaquimrocha joaquimrocha moved this from Proposed to Queued in Release Plan / Roadmap Jul 18, 2024
@joaquimrocha joaquimrocha added this to the v0.26.0 milestone Jul 31, 2024
@benlei
Copy link

benlei commented Jul 31, 2024

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).

@whitingj
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocker Completely prevents the user from using the software. enhancement New feature or request frontend Issues related to the frontend
Projects
Status: Blocked
Development

No branches or pull requests

4 participants