skupper
skupper copied to clipboard
`skupper version` shows no information if the cluster is unreacheable
Describe the bug
If $KUBECONFIG is set (or ~/.kube/config exists) and its configured cluster is inaccessible, the skupper version command returns an empty output.
$ skupper version
COMPONENT VERSION
$
How To Reproduce
Pick an existing kubeconfig file and change its server key to a closed port on localhost, such as 1234.
Then execute the skupper version command and inspect the output.
$ skupper version
COMPONENT VERSION
$ grep server $KUBECONFIG
server: https://localhost:1234
Expected behavior
This needs to be worked in light of #2019:
- if the intention is to show the running versions, an error message should be shown stating that the operation cannot be completed, as the cluster is not accessible.
- for baked-in images and environment variables, the command should return its information, in full, as it does not depend on the cluster.
Environment details
- Skupper CLI: 2.0.0
- Skupper Operator (if applicable): Not applicable
- Platform: Not applicable
Additional context Not applicable