Skip to content

Graduate flagz API to beta#137174

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

Graduate flagz API to beta#137174
k8s-ci-robot merged 1 commit intokubernetes:masterfrom
richabanker:flagz-beta

Conversation

@richabanker
Copy link
Copy Markdown
Contributor

@richabanker richabanker commented Feb 21, 2026 •
edited
Loading

What type of PR is this?

/kind feature

What this PR does / why we need it:

Graduates config.k8s.io.flagz from v1alpha1 to v1beta1

Which issue(s) this PR is related to:

Issue: kubernetes/enhancements#4828

Special notes for your reviewer:

Does this PR introduce a user-facing change?

config.k8s.io.flagz API is graduated to v1beta1

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

@k8s-ci-robot k8s-ci-robot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. release-note Denotes a PR that will be considered when it comes time to generate release notes. kind/feature Categorizes issue or PR as related to a new feature. do-not-merge/needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. area/apiserver area/code-generation area/kubelet area/test cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/api-change Categorizes issue or PR as related to adding, removing, or otherwise changing an API sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. sig/instrumentation Categorizes an issue or PR as relevant to SIG Instrumentation. sig/node Categorizes an issue or PR as relevant to SIG Node. labels Feb 21, 2026
@k8s-ci-robot k8s-ci-robot added sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. sig/testing Categorizes an issue or PR as relevant to SIG Testing. and removed do-not-merge/needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Feb 21, 2026
@github-project-automation github-project-automation Bot moved this to Needs Triage in SIG Instrumentation Feb 21, 2026
@github-project-automation github-project-automation Bot moved this to Needs Triage in SIG Scheduling Feb 21, 2026
@richabanker richabanker mentioned this pull request Feb 21, 2026
Open
30 tasks
@richabanker richabanker moved this from Needs Triage to In Progress in SIG Instrumentation Feb 28, 2026
@liggitt
Copy link
Copy Markdown
Member

liggitt commented Mar 3, 2026

/lgtm
/approve

@liggitt liggitt moved this from Changes requested to API review completed, 1.36 in API Reviews Mar 3, 2026
@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Mar 3, 2026
@k8s-ci-robot
Copy link
Copy Markdown
Contributor

k8s-ci-robot commented Mar 3, 2026

LGTM label has been added.

DetailsGit tree hash: 1a7d5829bd7304639a0d961bc2e81ac18d960985

@k8s-ci-robot
Copy link
Copy Markdown
Contributor

k8s-ci-robot commented Mar 3, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: liggitt, 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 approved Indicates a PR has been approved by an approver from all required OWNERS files. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. labels Mar 3, 2026
@k8s-ci-robot k8s-ci-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Mar 3, 2026
@k8s-ci-robot k8s-ci-robot requested a review from liggitt March 3, 2026 20:46
@k8s-ci-robot k8s-ci-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Mar 3, 2026
@richabanker
Copy link
Copy Markdown
Contributor Author

richabanker commented Mar 3, 2026 •
edited
Loading

@liggitt thanks for the reviews on this and statusz API graduations!
I resolved the merge conflicts on this one (after statusz PR got in), so it removed the lgtm, could you help tag it once again? Thanks!

@liggitt
Copy link
Copy Markdown
Member

liggitt commented Mar 3, 2026

/retest

unrelated test issue (but worth deflaking separately)

{Failed  === RUN   TestReadinessAggregatedAPIServiceDiscovery
    testserver.go:631: Resolved testserver package path to: "/home/prow/go/src/k8s.io/kubernetes/cmd/kube-apiserver/app/testing"
    testserver.go:429: runtime-config=map[]
    testserver.go:430: Starting kube-apiserver on port 46469...
    testserver.go:465: Waiting for /healthz to be ok...
    discovery_test.go:239: 
        	Error Trace:	/home/prow/go/src/k8s.io/kubernetes/test/integration/apiserver/discovery/discovery_test.go:239
        	Error:      	Received unexpected error:
        	            	failed to fetch v2 discovery: client rate limiter Wait returned an error: context deadline exceeded
        	Test:       	TestReadinessAggregatedAPIServiceDiscovery

@liggitt
Copy link
Copy Markdown
Member

liggitt commented Mar 3, 2026

/lgtm

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

k8s-ci-robot commented Mar 3, 2026

LGTM label has been added.

DetailsGit tree hash: 5ef1a5306fbdf2e1cfb09431cb44080a8e950331

@k8s-ci-robot k8s-ci-robot merged commit 5f18de6 into kubernetes:master Mar 3, 2026
12 of 13 checks passed
@k8s-ci-robot k8s-ci-robot added this to the v1.36 milestone Mar 3, 2026
@github-project-automation github-project-automation Bot moved this from In Progress to Done in SIG Instrumentation Mar 3, 2026
@github-project-automation github-project-automation Bot moved this from Needs Review to Done in SIG Scheduling Mar 3, 2026
@github-project-automation github-project-automation Bot moved this from Triage to Done in SIG Node CI/Test Board Mar 3, 2026
@richabanker richabanker mentioned this pull request Mar 4, 2026
Merged
@reylejano reylejano mentioned this pull request Mar 18, 2026
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@andrewsykim andrewsykim Awaiting requested review from andrewsykim

@kerthcet kerthcet Awaiting requested review from kerthcet

@liggitt liggitt Awaiting requested review from liggitt

Assignees

@liggitt liggitt

Labels

api-review Categorizes an issue or PR as actively needing an API review. approved Indicates a PR has been approved by an approver from all required OWNERS files. area/apiserver area/code-generation area/kubelet area/test cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/api-change Categorizes issue or PR as related to adding, removing, or otherwise changing an API kind/feature Categorizes issue or PR as related to a new feature. lgtm "Looks good to me", indicates that a PR is ready to be merged. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. release-note Denotes a PR that will be considered when it comes time to generate release notes. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. sig/instrumentation Categorizes an issue or PR as relevant to SIG Instrumentation. sig/node Categorizes an issue or PR as relevant to SIG Node. sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. sig/testing Categorizes an issue or PR as relevant to SIG Testing. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Projects

API Reviews
Status: API review completed, 1.36
SIG Instrumentation
Archived in project
SIG Node CI/Test Board
Status: Done
SIG Node: code and documentation PRs
Status: Done
SIG Scheduling
Archived in project

Milestone

v1.36

Development

Successfully merging this pull request may close these issues.

6 participants

@richabanker @Jefftree @liggitt @k8s-ci-robot @benjaminapetersen @helayoty