-
Notifications
You must be signed in to change notification settings - Fork 136
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
Change the way that Kubeconfig setting are managed at the project level to reduce confusion #3543
Comments
We will reintroduce this in #3541 with better config management |
Investigate if we can fix the underlying problem |
Possible solution: When we go back to the starting page after opening a project, if we go to the "Connect to Cluster" option, we should see the header using the Global Kubeconfig file, not the one from the project. |
We should implement a redux action that can reset the state of the app to remove the currently opened project |
Closing this because we've made a popup that notifies the user the connection will be closed when switching projects. |
Let's keep only the Global Settings for configuring the Kubeconfig file because it seems to be confusing setting up a kubeconfig file.
The text was updated successfully, but these errors were encountered: