-
Notifications
You must be signed in to change notification settings - Fork 14.6k
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
Incorrect cheat sheet entry: List all warning Events #40683
Comments
/triage accepted Thanks for reporting this! How about we document /retitle Incorrect cheat sheet entry: List all warning Events |
The above commands works for me on v1.27. But agree with suggestion #40683 (comment) to provide an example having the mention of namespace to get some useful output instead of |
It would be helpful if compatibility information for specific versions is clearly stated and a separate page for events should be added similar to other API resources. Also, v.1.27 is just released and even the AWS EKS doesn't support it yet. |
/remove-triage accepted Oops. I tested with an old kubectl version. We don't provide compatibility information for each subcommand of We could add a comment to that line to mention that older kubectl versions don't provide this subcommand. |
/remove-help |
The problem appears to be identical to #40582 and may be a duplicate. It seems that people are having trouble with the Refer: kubectl events enhancement |
I am closing the ticket as there is already version selection drop down at top right menu bar where you can select a version and it will provide commands specific to that version :) |
This is a Bug Report
Problem:
In the cheat sheet page, following command is suggested to list all warning events:
kubectl events --types=Warning
I get this error when I run this command
Proposed Solution:
I think it should be replaced by following:
kubectl get events --field-selector type=Warning
Page to Update:
https://kubernetes.io/docs/reference/kubectl/cheatsheet/#viewing-and-finding-resources
Kubernetes Version: v1.26.1
The text was updated successfully, but these errors were encountered: