Skip to content

Automated cherry pick of #137253: DRA: start scheduler after creating binding/non-binding slicesin Basicflow#137366

Merged
k8s-ci-robot merged 2 commits into
kubernetes:release-1.35from
tsj-30:automated-cherry-pick-of-#137253-upstream-release-1.35
Mar 4, 2026
Merged

Automated cherry pick of #137253: DRA: start scheduler after creating binding/non-binding slicesin Basicflow#137366
k8s-ci-robot merged 2 commits into
kubernetes:release-1.35from
tsj-30:automated-cherry-pick-of-#137253-upstream-release-1.35

Conversation

@tsj-30

@tsj-30 tsj-30 commented Mar 3, 2026

Copy link
Copy Markdown
Contributor

Cherry pick of #137253 on release-1.35.

#137253: DRA: start scheduler after creating binding/non-binding slicesin Basicflow

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

NONE

@k8s-ci-robot k8s-ci-robot added this to the v1.35 milestone Mar 3, 2026
@k8s-ci-robot k8s-ci-robot added release-note-none Denotes a PR that doesn't merit a release note. do-not-merge/cherry-pick-not-approved Indicates that a PR is not yet approved to merge into a release branch. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. do-not-merge/needs-kind Indicates a PR lacks a `kind/foo` label and requires one. do-not-merge/needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Mar 3, 2026
@k8s-ci-robot

Copy link
Copy Markdown
Contributor

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. area/test sig/node Categorizes an issue or PR as relevant to SIG Node. sig/testing Categorizes an issue or PR as relevant to SIG Testing. labels Mar 3, 2026
@k8s-ci-robot k8s-ci-robot added wg/device-management Categorizes an issue or PR as relevant to WG Device Management. and removed do-not-merge/needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Mar 3, 2026
@k8s-ci-robot k8s-ci-robot requested review from bart0sh and pohly March 3, 2026 10:51
@pohly

pohly commented Mar 3, 2026

Copy link
Copy Markdown
Contributor

/lgtm
/approve

This fixes a flake.

/cc kubernetes/release-managers

@k8s-ci-robot k8s-ci-robot requested a review from a team March 3, 2026 11:06
@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

LGTM label has been added.

DetailsGit tree hash: a2ac9d2724ac309d31e2b4bc917c8e4afd5b1a58

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 3, 2026
@pohly pohly moved this from 🆕 New to 👀 In review in Dynamic Resource Allocation Mar 3, 2026
@tsj-30

tsj-30 commented Mar 3, 2026

Copy link
Copy Markdown
Contributor Author

Thank you for the LGTM @pohly 😄

@Rajalakshmi-Girish

Rajalakshmi-Girish commented Mar 3, 2026

Copy link
Copy Markdown
Contributor

@xmudrii Can you please have a look at this one too?

@xmudrii

xmudrii commented Mar 4, 2026

Copy link
Copy Markdown
Member

/kind flake

@k8s-ci-robot k8s-ci-robot added kind/flake Categorizes issue or PR as related to a flaky test. and removed do-not-merge/needs-kind Indicates a PR lacks a `kind/foo` label and requires one. labels Mar 4, 2026

@xmudrii xmudrii left a comment

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.

/lgtm
/approve

@github-project-automation github-project-automation Bot moved this from Triage to Needs Approver in SIG Node: code and documentation PRs Mar 4, 2026
@github-project-automation github-project-automation Bot moved this from Triage to PRs - Needs Approver in SIG Node CI/Test Board Mar 4, 2026
@k8s-ci-robot k8s-ci-robot added cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. and removed do-not-merge/cherry-pick-not-approved Indicates that a PR is not yet approved to merge into a release branch. labels Mar 4, 2026
@k8s-ci-robot

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: pohly, tsj-30, xmudrii

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 merged commit 60ebb8a into kubernetes:release-1.35 Mar 4, 2026
24 checks passed
@github-project-automation github-project-automation Bot moved this from PRs - Needs Approver to Done in SIG Node CI/Test Board Mar 4, 2026
@github-project-automation github-project-automation Bot moved this from Needs Approver to Done in SIG Node: code and documentation PRs Mar 4, 2026
@pohly pohly moved this from 👀 In review to ✅ Done in Dynamic Resource Allocation Mar 4, 2026
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. area/test cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/flake Categorizes issue or PR as related to a flaky test. 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. 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/node Categorizes an issue or PR as relevant to SIG Node. sig/testing Categorizes an issue or PR as relevant to SIG Testing. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. wg/device-management Categorizes an issue or PR as relevant to WG Device Management.

Development

Successfully merging this pull request may close these issues.

5 participants