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.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
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
/help
/remove-lifecycle reotten
@vincepri:
This request has been marked as needing help from a contributor.
Please ensure the request meets the requirements listed here.
If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.
In response to this:
/milestone v0.9.x
/help
/remove-lifecycle reotten
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.
For more information please see the contributor guide
In response to this:
/assign @MadhavJivrajani
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:
pkg/client/client.go, a new default warning handler is set as mentioned here.
Most helpful comment
/assign @MadhavJivrajani