Skip to content

Conversation

vahit
Copy link

@vahit vahit commented Nov 16, 2018

We can fix #296 issue with a small change in code because the kubectl config command use from first config file to read and write current-context value.

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

Successfully merging this pull request may close these issues.

k8s current-context in multi-cluster
1 participant