Terminal kubectl context is not set to the cluster you're currently viewing #373
Description
Describe the bug
When the terminal is opened, I would expect the kubectl context to be set to the cluster you're viewing. This makes running kubectl commands confusing as you have to manually switch each time
To reproduce
Steps to reproduce the behavior:
- Select a different cluster in skyhook radar
- Open the terminal
- When running kubectl config current-context, it is not set to the cluster you're viewing
Expected behavior
The terminal should automatically be set to the context you're viewing