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

Toggle to disable checking clusters on startup (windows). #2623

Open
greenaar opened this issue Dec 1, 2024 · 2 comments
Open

Toggle to disable checking clusters on startup (windows). #2623

greenaar opened this issue Dec 1, 2024 · 2 comments
Labels
duplicate This issue or pull request already exists enhancement New feature or request windows Issues related to Windows or WSL

Comments

@greenaar
Copy link

greenaar commented Dec 1, 2024

Is your feature request related to a problem? Please describe the impact that the lack of the feature requested is creating.

When starting on windows, EVERY cluster is checked. this opens N+1 terminal windows to run the companion kubectl command. This happens EVERY time you go back to the main window. Every new window also steals keyboard/mouse focus.

Describe the solution you'd like

Give me the option to turn that behaviour off. I wouldn't mind some granularity, but i'd take 'don't check until i select a cluster'

What users will benefit from this feature?

Windows users certainly will benefit. I have 9 clusters in my kubeconfig, and switching back to the main page is a visual assault.

Are you able to implement this feature?

Sadly not.

Additional context

Alternatively, if you can suppress opening terminal windows with each command run, that would also serve.

@greenaar greenaar added the enhancement New feature or request label Dec 1, 2024
@dosubot dosubot bot added the windows Issues related to Windows or WSL label Dec 1, 2024
@joaquimrocha
Copy link
Collaborator

@greenaar , thanks. Indeed, this is in our plans at #2165 .
Can you confirm one thing for me: how is the authentication in your clusters? I guess you are using the exec plugin of kube config? Would it work if we connected automatically to all clusters/contexts except those with that exec plugin?
In any case, I think a global setting like this would work:
Automatically connect to clusters: [ ] All [ ] None [ ] Only these: _____

@joaquimrocha joaquimrocha added the duplicate This issue or pull request already exists label Dec 4, 2024
@greenaar
Copy link
Author

greenaar commented Dec 5, 2024

@joaquimrocha the problematic clusters are all in EKS, so there's a whole authentication layer (2fa) that needs to occur before they are available. As a rule, I don't want to check them until I've authorized, which may not be at the point I start this application (I have another cluster which doesn't need any additional authentication which i use more often).

Your proposed solution would be ideal - in my case I'd probably always default it to 'None', and then connect to them as needed and intentionally. I would also suggest that be the default behavior, as there are a number of reasons to not automatically query clusters - regardless, having that option would be welcome and appreciated.

Thanks for taking this seriously. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists enhancement New feature or request windows Issues related to Windows or WSL
Projects
Development

No branches or pull requests

2 participants