kflex init does NOT store the name of the hosting context. That is done later when kflex create or kflex ctx $cpname is used to switch away. This opens an unnecessary window for problems: the user might (unknowingly or inadvertently) use kubectl config use-context for some reason before doing kflex create.
If the name of the hosting context is not currently stored in the user's kubeconfig file, and the current context is the hosting cluster context, kflex ctx does not store the context name. This is unnecessarily missing an opportunity to recover needed information.
kflex init
does NOT store the name of the hosting context. That is done later whenkflex create
orkflex ctx $cpname
is used to switch away. This opens an unnecessary window for problems: the user might (unknowingly or inadvertently) usekubectl config use-context
for some reason before doingkflex create
.kflex ctx
does not store the context name. This is unnecessarily missing an opportunity to recover needed information.