Closed RedbackThomson closed 4 months ago
@sttts ran the following commands and provided the output:
gcloud get credentials
up ctx
up ctx ./default
up ctx ./ctp-kine
up ctx .
Kubeconfig context "upbound": Upbound organizations
up ctx -
up ctx should work identically in cloud as it does in disconnected spaces.
First part of the fix https://github.com/upbound/up/pull/491
I can successfully validate that all of these commands are now working as expected! ❤️
What happened?
@sttts ran the following commands and provided the output:
gcloud get credentials
up ctx
✅up ctx ./default
✅up ctx ./ctp-kine
❌up ctx .
broken due to upper command:Kubeconfig context "upbound": Upbound organizations
, should be the group. ❌up ctx
interactively going into ctp-kine ✅up ctx .
broken againKubeconfig context "upbound": Upbound organizations
❌up ctx -
has wrong output:Kubeconfig context "upbound": Upbound organizations
, ❌ and I lost the group ❌up ctx
– shows the organizations again although I am on the hub ❌up ctx
should work identically in cloud as it does in disconnected spaces.How can we reproduce it?
What environment did it happen in?