KEP-4828: graduate ComponentFlagz to beta#5806
KEP-4828: graduate ComponentFlagz to beta#5806k8s-ci-robot merged 1 commit intokubernetes:masterfrom
Conversation
76e86fc to
2fd8087
Compare
|
Are there any changes to the feature planned for beta? |
There's one open PR to extend the API to support YAML and CBOR format kubernetes/kubernetes#135309 Other than that I think we'd need to also graduate the API https://github.com/kubernetes/kubernetes/tree/master/staging/src/k8s.io/apiserver/pkg/server/flagz/api to beta. |
|
Do those changes need to be reflected in the KEP at all? |
|
The requirement for API graduation is already in the KEP. I can add an update to specify the other YAML/CBOR formats support though. Will do so. |
|
/retitle KEP-4828: graduate ComponentFlagz to beta |
2fd8087 to
fa054dd
Compare
Done now |
b0bdc17 to
3addd43
Compare
3addd43 to
6873ac6
Compare
|
ping SIG approver @dgrisonnet for review. |
There was a problem hiding this comment.
Please add a metric to count when it is hit and the return status.
There was a problem hiding this comment.
would a metric be useful here? I dont think people want to set an alert for a metric to know when a debugging endpoint was requested?
There was a problem hiding this comment.
@dashpole or @dgrisonnet for thoughts about whether we need metrics for zpages.
There was a problem hiding this comment.
@johnbelamaric after thinking more on this, I think we could delegate metrics for these endpoints for future only if/when the need arises to monitor these endpoints. Generally we want these endpoints to behave the same way as other existing debugging/monitoring endpoints like /healthz, /livez, /metrics - we dont have dedicated metrics for these endpoints too.
Does that sound ok to you?
There was a problem hiding this comment.
I think each component should instrument the /flagz and /statusz endpoint similarly to the health endpoints today. For example the apiserver records requests made to these endpoints in its apiserver_request_total and apiserver_request_duration_seconds metrics: https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/apiserver/pkg/server/healthz/healthz.go#L212
Although the zpages endpoints are unlikely to be DDOSed, there is always a possibility and we would need this information in the http metrics to be aware of that situation
There was a problem hiding this comment.
Yeah. Abuse is the main thing it can help identify.
There was a problem hiding this comment.
Oh I missed noting that we do have coverage for healthz, livez, readyz endpoints via the apiserver_request_total and apiserver_request_duration_seconds metrics. Thanks for pointing that out!
Updated the KEP to make flagz follow the same pattern. Also updated statusz KEP to state the same here #5910
Thanks both for the discussion!
6873ac6 to
44f4f87
Compare
44f4f87 to
058b513
Compare
058b513 to
0b63c98
Compare
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dgrisonnet, johnbelamaric, richabanker The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Graduate ComponentFlagz to beta