Skip to content

Automated cherry pick of #138584: [chore] test/compatibility_lifecycle: resolve feature names from variables#138974

Open
stmcginnis wants to merge 1 commit into
kubernetes:release-1.36from
stmcginnis:automated-cherry-pick-of-#138584-upstream-release-1.36
Open

Automated cherry pick of #138584: [chore] test/compatibility_lifecycle: resolve feature names from variables#138974
stmcginnis wants to merge 1 commit into
kubernetes:release-1.36from
stmcginnis:automated-cherry-pick-of-#138584-upstream-release-1.36

Conversation

@stmcginnis
Copy link
Copy Markdown
Contributor

@stmcginnis stmcginnis commented May 11, 2026

Cherry pick of #138584 on release-1.36.

#138584: [chore] test/compatibility_lifecycle: resolve feature names from variables

For details on the cherry pick process, see the cherry pick requests page.

What type of PR is this?

/kind failing-test

@siyuanfoundation @stmcginnis
test/compatibility_lifecycle: resolve feature names from variables
720f13b 
Signed-off-by: Siyuan Zhang <sizhang@google.com>
@k8s-ci-robot k8s-ci-robot added the do-not-merge/cherry-pick-not-approved Indicates that a PR is not yet approved to merge into a release branch. label May 11, 2026
@k8s-ci-robot k8s-ci-robot added this to the v1.36 milestone May 11, 2026
@k8s-ci-robot k8s-ci-robot added kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels May 11, 2026
@k8s-ci-robot
Copy link
Copy Markdown
Contributor

k8s-ci-robot commented May 11, 2026

This cherry pick PR is for a release branch and has not yet been approved by Release Managers.
Adding the do-not-merge/cherry-pick-not-approved label.

To merge this cherry pick, it must first be approved (/lgtm + /approve) by the relevant OWNERS.

If you didn't cherry-pick this change to all supported release branches, please leave a comment describing why other cherry-picks are not needed to speed up the review process.

If you're not sure is it required to cherry-pick this change to all supported release branches, please consult the cherry-pick guidelines document.

AFTER it has been approved by code owners, please leave the following comment on a line by itself, with no leading whitespace: /cc kubernetes/release-managers

(This command will request a cherry pick review from Release Managers and should work for all GitHub users, whether they are members of the Kubernetes GitHub organization or not.)

For details on the patch release process and schedule, see the Patch Releases page.

Details

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-sigs/prow repository.

@k8s-ci-robot k8s-ci-robot added do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. do-not-merge/needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels May 11, 2026
@k8s-ci-robot
Copy link
Copy Markdown
Contributor

k8s-ci-robot commented May 11, 2026

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Details

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-sigs/prow repository.

@k8s-ci-robot k8s-ci-robot added 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. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels May 11, 2026
@stmcginnis stmcginnis closed this May 11, 2026
@stmcginnis stmcginnis deleted the automated-cherry-pick-of-#138584-upstream-release-1.36 branch May 11, 2026 20:45
@k8s-ci-robot k8s-ci-robot requested a review from jayunit100 May 11, 2026 20:46
@k8s-ci-robot
Copy link
Copy Markdown
Contributor

k8s-ci-robot commented May 11, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: stmcginnis
Once this PR has been reviewed and has the lgtm label, please assign luxas for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found 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 requested a review from towca May 11, 2026 20:47
@k8s-ci-robot k8s-ci-robot added area/test sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. 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 May 11, 2026
@stmcginnis stmcginnis restored the automated-cherry-pick-of-#138584-upstream-release-1.36 branch May 11, 2026 20:47
@stmcginnis stmcginnis reopened this May 11, 2026
@stmcginnis
Copy link
Copy Markdown
Contributor Author

stmcginnis commented May 11, 2026

/release-note-none

@k8s-ci-robot k8s-ci-robot added release-note-none Denotes a PR that doesn't merit a release note. and removed do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. labels May 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@jayunit100 jayunit100 Awaiting requested review from jayunit100

@towca towca Awaiting requested review from towca

Assignees

No one assigned

Labels

area/test cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. do-not-merge/cherry-pick-not-approved Indicates that a PR is not yet approved to merge into a release branch. kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. release-note-none Denotes a PR that doesn't merit a release note. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. sig/testing Categorizes an issue or PR as relevant to SIG Testing. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

[sig-release] Bug Triage
Status: No status

Milestone

v1.36

Development

Successfully merging this pull request may close these issues.

4 participants

@stmcginnis @k8s-ci-robot @k8s-infra-ci-robot @siyuanfoundation