-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Surface warnings sent by apiserver via client-go #1150
Comments
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Hi @vincepri, Should not it be prioritized for the next milestone since soon we will be bumping the k8s api that will no longer supported the deprecated ones? |
Possibly yeah |
/milestone v0.9.x |
@vincepri: Please ensure the request meets the requirements listed here. If this request no longer meets these requirements, the label can be removed In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/remove-lifecycle rotten |
/assign @MadhavJivrajani |
@palnabarun: GitHub didn't allow me to assign the following users: MadhavJivrajani. Note that only kubernetes-sigs members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Hi! I'd like to take this up 😄 /assign |
Hi! After going through the linked blog post and the related KEP, this is what I thought of implementing and I was hoping to get some feedback on the same:
|
We should look into surfacing warnings sent in responses by 1.19+ API servers.
Examples of these warnings include:
See https://kubernetes.io/blog/2020/09/03/warnings/ for details.
The text was updated successfully, but these errors were encountered: