Currently, the system manages only one K8S certificate.
The underlying K8S connection is resolved by the current ~/.kube/config because it uses only the plain kubectl command.
Solution requirements
store multiple certificates for different clusters
selection on which cluster the user wants to work (based on the ~./kube/config file)
What is the problem?
Currently, the system manages only one K8S certificate. The underlying K8S connection is resolved by the current
~/.kube/config
because it uses only the plainkubectl
command.Solution requirements
~./kube/config
file)