feature: enable me to work with more than one system

[MikeSpreitzer]

Feature Description

I switch between multiple distributed systems. One is a triple of OCP clusters on the IBM Cloud. Another is my work testing KubeStellar PRs, which is done with triples of Kind clusters or k3s clusters. I would like to be able to set up a set of kubeconfig contexts for each system, coexisting concurrently. kflex ctx $cp_name is not quite up to the task, because it names several sorts of entries in the kubeconfig based on the $cp_name: a context, a cluster, and a user. kubectl config rename-context is a thing, but renaming a cluster and a user is not. I could do the edits by hand, but that is tedious and easy to mess up.

Proposed Solution

Add an option on kflex ctx $cp_name that conveys an alternative to $cp_name to use in the names of the cluster, user, and context.

Want to contribute?

• I would like to work on this issue.

Additional Context

No response