-
Notifications
You must be signed in to change notification settings - Fork 39.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
kubectl get componentstatus
fails to write as table
#83024
Comments
/sig cli |
This actually means the apiserver is not returning table results. /remove-sig cli not sure which sig owns this API, so taking a guess |
Isn't component status deprecated? |
Not officially. It got stuck in the "the replacement must be available before it can be deprecated" trap, despite being fundamentally flawed and inapplicable to many topologies. |
I reopened the issue to push forward deprecation in kubernetes/enhancements#553 (comment) |
kubectl version VDS: Intel Xeon - 2.6Ghz, RAM 2 Gb, HDD — 30 Gb cat /etc/os-release uname -a Flanel |
I get the same issue with the v1.16.2 release
|
|
Duplicate of kubernetes/kubectl#762, not sure which one should be closed. |
Resolved in 1.17.0 |
What happened:
What you expected to happen:
get componentstatus
should be able to have its results formated as a table by kubectlHow to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
-o yaml or json work as expected
Environment:
kubectl version
):also ran against 1.16.0 servers with same result
AWS
cat /etc/os-release
):uname -a
):Self-hosted
The text was updated successfully, but these errors were encountered: