You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You currently cannot watch 2+ contexts in parallel (which can be a problem though bcs too many watches eat memory, cpu etc.).
Lens lists all of them (like we currently do). You can also have several clusters "active" at the same time. They dont list individual items like pods in the navigator though, only the cathegory "Pods". You can list the pods in a editor that is watching them come and go though. That's how they avoid too many watches.
The drawback is though, that you only see ex. all the pods that belong to a deployment after opening the editor that lists all the deployments and then open properties for your deployment (2 clicks while we list them right in the tree).
Jetbrains Kubernetes Plugin has a different approach. It requires the user to explicitly add contexts (we list all available ones, KUBECONFIG env var or main config file)
We could also improve the user experience by improvements when switching contexts instead. Bookmarks, restoring previous expansion states, etc. would help a lot. This could be a simple was to improve the current limitation since switching in our plugin is fast.
The text was updated successfully, but these errors were encountered:
related to #162
You currently cannot watch 2+ contexts in parallel (which can be a problem though bcs too many watches eat memory, cpu etc.).
Lens lists all of them (like we currently do). You can also have several clusters "active" at the same time. They dont list individual items like pods in the navigator though, only the cathegory "Pods". You can list the pods in a editor that is watching them come and go though. That's how they avoid too many watches.
![Image](https://private-user-images.githubusercontent.com/25126/411358137-4d8edb86-0ad1-4d40-b38d-6f329448b6ba.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzk5NzM3NDUsIm5iZiI6MTczOTk3MzQ0NSwicGF0aCI6Ii8yNTEyNi80MTEzNTgxMzctNGQ4ZWRiODYtMGFkMS00ZDQwLWIzOGQtNmYzMjk0NDhiNmJhLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTklMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjE5VDEzNTcyNVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPThlZTJmOWJhM2QyNWIxN2RmNjg1OTc0MjRhZTE4NDFiNzFlZTBhOGYzYWJiZjkzYTk1OTgzODRkY2JlODY5MDMmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.9krK9wiYsj4awxP68B2i9IrTSVxbz1NPah_M56wche8)
The drawback is though, that you only see ex. all the pods that belong to a deployment after opening the editor that lists all the deployments and then open properties for your deployment (2 clicks while we list them right in the tree).
Jetbrains Kubernetes Plugin has a different approach. It requires the user to explicitly add contexts (we list all available ones, KUBECONFIG env var or main config file)
![](https://private-user-images.githubusercontent.com/25126/411358409-4e690392-fe33-4202-bd79-ec14800f64ec.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzk5NzM3NDUsIm5iZiI6MTczOTk3MzQ0NSwicGF0aCI6Ii8yNTEyNi80MTEzNTg0MDktNGU2OTAzOTItZmUzMy00MjAyLWJkNzktZWMxNDgwMGY2NGVjLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTklMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjE5VDEzNTcyNVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTNlNTVhNzY1NmQ3ZGQ4Y2E1NThjNDYxZmE1ODE4YzM2ODM5MDllZmJkNTRkZTUzZDhjMzRiMjhjNTVjYTgxY2QmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.iICnsxCJykyxwXShzEQyMUYva7tPVL8LxG3poK7FVeI)
We could also improve the user experience by improvements when switching contexts instead. Bookmarks, restoring previous expansion states, etc. would help a lot. This could be a simple was to improve the current limitation since switching in our plugin is fast.
The text was updated successfully, but these errors were encountered: