When you run up ctp kubeconfig get with wrong token, account or any other argument, it does not fail as long as it's able to construct kubeconfig YAML. Then user gets error in kubectl when they try to access MCP like api is not found which is misleading.
How could Upbound help solve your problem?
up ctp kubeconfig get should check whether the kubeconfig it produces actually works before returning to user.
What problem are you facing?
When you run
up ctp kubeconfig getwith wrong token, account or any other argument, it does not fail as long as it's able to construct kubeconfig YAML. Then user gets error inkubectlwhen they try to access MCP likeapi is not foundwhich is misleading.How could Upbound help solve your problem?
up ctp kubeconfig getshould check whether the kubeconfig it produces actually works before returning to user.