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

Feature request: separate configuration for cluster login #410

Open
223311 opened this issue Aug 20, 2022 · 2 comments
Open

Feature request: separate configuration for cluster login #410

223311 opened this issue Aug 20, 2022 · 2 comments

Comments

@223311
Copy link

223311 commented Aug 20, 2022

while opening the kubenav it automatically login to the k8 cluster, instead of that, if we have one cluster page and show a list of clusters based on user input it will log in to that cluster.

@mjf
Copy link

mjf commented Dec 7, 2022

I also do not like the idea that kubenav does login automatically! A per cluster option SHOULD be provided to turn the autologin on/off (with default to off). That would be very helpful. I also would like to turn off attempts to login to specific cluster already doing failing attempts to autologin completely, if in the need.

The status page @223311 suggested is generally a good idea. For each cluster it should distrinquish few things to get some idea of the overall situation, for example:

  • autologin is off/disabled (gray 0/0),
  • autologin is on/enabled but it is failing (yellow, counter of failed attempts of max. attempts i.e. 30/100),
  • login failed too many times and was switched off (red/gray, 100/100),
  • login was succesfull (green 3/100, perhaps with some additional top-level information from stats).

You can combine the login state (an keep it) with the autologin configured state, for example if somebody switch of the autologin after succesful login to a cluster it could be denoted by a circle gray (autologin is off) and green (last known login was successfull).

I am unsure about all this but the truth is I would like to get such simple overview, especially if there were many clusters I want too there may be an issue at the first glance, therefor an overall cluster state would be also helpful on the suggested status page with at least: % RAM / # RAM, % CPU / # CORES, % FAILING PODs / # SCHEDULED PODs (and kept so that you always see the last known state)...

@ricoberger
Copy link
Member

Hi @223311 and @mjf, the first feature request is now implemented in v4 via #437 and should be available in the next beta version. The feature can be enabled in the setting, so that a screen with all configured clusters is shown during the start of the app instead of the default overview screen.

Regarding the second request: I like the idea of having a screen with all clusters and the mentioned information and will work on this, but I'm not sure if this will be already included in the next major release.

Currently I'm not sure if it would make sense to add this to the already existing clusters screen or to the new clusters screen which can be shown when the app is started. We have to make a lot of requests to get all these information and I want to keep this screens fast, so that I would prefer to add a new screen, which can be accessed directly from the home screen or from the plugins section.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants