Skip to content

KEP-4828: graduate ComponentFlagz to beta#5806

Merged
k8s-ci-robot merged 1 commit intokubernetes:masterfrom
richabanker:flagz-beta
Feb 10, 2026
Merged

KEP-4828: graduate ComponentFlagz to beta#5806
k8s-ci-robot merged 1 commit intokubernetes:masterfrom
richabanker:flagz-beta

Conversation

@richabanker
Copy link
Copy Markdown
Contributor

  • One-line PR description:
    Graduate ComponentFlagz to beta

@k8s-ci-robot k8s-ci-robot added kind/kep Categorizes KEP tracking issues and PRs modifying the KEP directory sig/instrumentation Categorizes an issue or PR as relevant to SIG Instrumentation. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels Jan 16, 2026
@dashpole
Copy link
Copy Markdown
Contributor

Are there any changes to the feature planned for beta?

@richabanker
Copy link
Copy Markdown
Contributor Author

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.

@dashpole
Copy link
Copy Markdown
Contributor

Do those changes need to be reflected in the KEP at all?

@richabanker
Copy link
Copy Markdown
Contributor Author

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.

@lmktfy
Copy link
Copy Markdown
Member

lmktfy commented Jan 27, 2026

/retitle KEP-4828: graduate ComponentFlagz to beta

@k8s-ci-robot k8s-ci-robot changed the title Graduate ComponentFlagz to beta KEP-4828: graduate ComponentFlagz to beta Jan 27, 2026
@richabanker
Copy link
Copy Markdown
Contributor Author

Do those changes need to be reflected in the KEP at all?

Done now

@richabanker richabanker force-pushed the flagz-beta branch 2 times, most recently from b0bdc17 to 3addd43 Compare January 30, 2026 20:25
@k8s-ci-robot k8s-ci-robot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Jan 30, 2026
@richabanker
Copy link
Copy Markdown
Contributor Author

ping SIG approver @dgrisonnet for review.

Copy link
Copy Markdown
Member

@dgrisonnet dgrisonnet left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm
/approve

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jan 30, 2026
@pmengelbert pmengelbert mentioned this pull request Feb 2, 2026
30 tasks
Comment thread keps/sig-instrumentation/4828-component-flagz/README.md Outdated
Comment thread keps/sig-instrumentation/4828-component-flagz/README.md Outdated
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please add a metric to count when it is hit and the return status.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@dashpole or @dgrisonnet for thoughts about whether we need metrics for zpages.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@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?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah. Abuse is the main thing it can help identify.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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!

@k8s-ci-robot k8s-ci-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Feb 9, 2026
@johnbelamaric
Copy link
Copy Markdown
Member

/approve
/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Feb 10, 2026
@k8s-ci-robot
Copy link
Copy Markdown
Contributor

[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

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 10, 2026
@k8s-ci-robot k8s-ci-robot merged commit 84c6b0b into kubernetes:master Feb 10, 2026
4 checks passed
@k8s-ci-robot k8s-ci-robot added this to the v1.36 milestone Feb 10, 2026
@richabanker richabanker deleted the flagz-beta branch February 10, 2026 21:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/kep Categorizes KEP tracking issues and PRs modifying the KEP directory lgtm "Looks good to me", indicates that a PR is ready to be merged. sig/instrumentation Categorizes an issue or PR as relevant to SIG Instrumentation. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants