Currently, the selection of contexts available in up ctx depends on the currently selected kubeconfig context:
If there's no kubeconfig, up ctx shows available cloud spaces.
If the current kubeconfig context doesn't have a space installed in it (i.e., is a normal Kubernetes cluster without Spaces installed), up ctx shows available cloud spaces.
If the current kubeconfig context is a cloud space, up ctx shows available cloud spaces.
If the current kubeconfig context is a self-hosted space, up ctx shows only groups and control planes in that space (regardless of whether the space is connected or disconnected). The only way to get back to the list of cloud spaces is to manually change the kubeconfig context outside of up.
How could Upbound help solve your problem?
Make it possible to navigate between cloud spaces, connected spaces, and self-hosted spaces regardless of the current kubeconfig context.
What problem are you facing?
Currently, the selection of contexts available in
up ctxdepends on the currently selected kubeconfig context:up ctxshows available cloud spaces.up ctxshows available cloud spaces.up ctxshows available cloud spaces.up ctxshows only groups and control planes in that space (regardless of whether the space is connected or disconnected). The only way to get back to the list of cloud spaces is to manually change the kubeconfig context outside ofup.How could Upbound help solve your problem?
Make it possible to navigate between cloud spaces, connected spaces, and self-hosted spaces regardless of the current kubeconfig context.