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
KEP 1693: Warning mechanism for use of deprecated APIs #1694
Conversation
93197c7
to
3d64a7b
Compare
43a3e89
to
af5bf39
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it sounds reasonable, I'm not clear on some of the details but the instrumentation stuff looks pretty sensible to me.
|
/lgtm for the metrics stuff as discussed offline |
|
/lgtm |
|
/lgtm (restamp) from sig-instrumentation |
|
Looks good to me, thanks! |
| 2. log to stderr with a `Warning:` prefix | ||
| 3. color the `Warning:` prefix if stderr is a terminal and `$TERM != "dumb"` and `$NO_COLOR` is unset | ||
|
|
||
| In kube-apiserver and kube-controller-manager, configure the process-wide handler to ignore warnings |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
scheduler?
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: lavalamp, liggitt, logicalhan The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
Will keep provisional until all reviewers get a shot at this, then get acks from approvers before flipping to implementable. I also added it to agendas for the upcoming SIG meetings to field any questions. |
|
Review continued in #1697, fixed a couple typos and added whitespace bits to allow adding comments to any lines |
This proposes a mechanism for surfacing use of deprecated APIs to users via
Warningheaders, and to administrators via metrics/audit events.Proof-of-concept at kubernetes/kubernetes#73032
/sig api-machinery architecture cli instrumentation