Skip to content

OCPBUGS-63213: Add priority field to prevent early shutdown#865

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
CoreyCook8:patch-1
Oct 14, 2025
Merged

OCPBUGS-63213: Add priority field to prevent early shutdown#865
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
CoreyCook8:patch-1

Conversation

@CoreyCook8
Copy link
Copy Markdown
Contributor

Based on the issue described here : kubernetes/kubernetes#133442

priorityClassName is currently ignored by Kubelet for static pod files so setting this value has no impact on the gracefulShutdown order causing the static pods to start to be killed as soon as shutdown begins.

To prevent this we must set priority explicitly

@openshift-ci openshift-ci Bot requested review from deads2k and ingvagabund August 29, 2025 17:21
@openshift-ci openshift-ci Bot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Aug 29, 2025
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Aug 29, 2025

Hi @CoreyCook8. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

@CoreyCook8
Copy link
Copy Markdown
Contributor Author

👋 @ingvagabund could I get an ok-to-test on this so we can merge when the E2E test PR merges in? 🙏

@CoreyCook8
Copy link
Copy Markdown
Contributor Author

👋 @ingvagabund could I get an ok-to-test on this so we can merge when the E2E test PR merges in? 🙏

@ingvagabund @deads2k ping on this 🙏

@ingvagabund
Copy link
Copy Markdown
Member

/ok-to-test

@openshift-ci openshift-ci Bot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Oct 13, 2025
@ingvagabund
Copy link
Copy Markdown
Member

/approve
/lgtm

1 similar comment
@ingvagabund
Copy link
Copy Markdown
Member

/approve
/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Oct 13, 2025
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Oct 13, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: CoreyCook8, ingvagabund

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

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 13, 2025
@ingvagabund
Copy link
Copy Markdown
Member

/verified by ci/prow/e2e-aws-operator

The operator needs to see the mirrored pod up and running. The KA admission plugin will fail when the priority class number is different from what is normally defined.

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Oct 14, 2025
@openshift-ci-robot
Copy link
Copy Markdown

@ingvagabund: This PR has been marked as verified by ci/prow/e2e-aws-operator.

Details

In response to this:

/verified by ci/prow/e2e-aws-operator

The operator needs to see the mirrored pod up and running. The KA admission plugin will fail when the priority class number is different from what is normally defined.

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 openshift-eng/jira-lifecycle-plugin repository.

@ingvagabund
Copy link
Copy Markdown
Member

/re-title no-jira: Add priority field to prevent early shutdown

@ingvagabund
Copy link
Copy Markdown
Member

/retitle no-jira: Add priority field to prevent early shutdown

@openshift-ci openshift-ci Bot changed the title Add priority field to prevent early shutdown no-jira: Add priority field to prevent early shutdown Oct 14, 2025
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Oct 14, 2025
@openshift-ci-robot
Copy link
Copy Markdown

@CoreyCook8: This pull request explicitly references no jira issue.

Details

In response to this:

Based on the issue described here : kubernetes/kubernetes#133442

priorityClassName is currently ignored by Kubelet for static pod files so setting this value has no impact on the gracefulShutdown order causing the static pods to start to be killed as soon as shutdown begins.

To prevent this we must set priority explicitly

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot
Copy link
Copy Markdown

/retest-required

Remaining retests: 0 against base HEAD 310bd06 and 2 for PR HEAD a8fd579 in total

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Oct 14, 2025

@CoreyCook8: all tests passed!

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

@openshift-merge-bot openshift-merge-bot Bot merged commit 52b7857 into openshift:main Oct 14, 2025
13 checks passed
@dinhxuanvu
Copy link
Copy Markdown
Contributor

/cherry-pick release-4.20

@openshift-cherrypick-robot
Copy link
Copy Markdown

@dinhxuanvu: new pull request created: #890

Details

In response to this:

/cherry-pick release-4.20

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.

@sanchezl
Copy link
Copy Markdown
Contributor

/retitle OCPBUGS-63213: Add priority field to prevent early shutdown

@openshift-ci openshift-ci Bot changed the title no-jira: Add priority field to prevent early shutdown OCPBUGS-63213: Add priority field to prevent early shutdown Jan 28, 2026
@openshift-ci-robot
Copy link
Copy Markdown

@CoreyCook8: Jira Issue Verification Checks: Jira Issue OCPBUGS-63213
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-63213 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Details

In response to this:

Based on the issue described here : kubernetes/kubernetes#133442

priorityClassName is currently ignored by Kubelet for static pod files so setting this value has no impact on the gracefulShutdown order causing the static pods to start to be killed as soon as shutdown begins.

To prevent this we must set priority explicitly

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 openshift-eng/jira-lifecycle-plugin repository.

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. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants