Skip to content

OPRUN-4588: use AlwaysAllow UnhealthyPodEvictionPolicy option in PDBs#1280

Open
atiratree wants to merge 1 commit intoopenshift:mainfrom
atiratree:pdb
Open

OPRUN-4588: use AlwaysAllow UnhealthyPodEvictionPolicy option in PDBs#1280
atiratree wants to merge 1 commit intoopenshift:mainfrom
atiratree:pdb

Conversation

@atiratree
Copy link
Copy Markdown
Member

@atiratree atiratree commented Apr 23, 2026

Allow eviction of unhealthy (not ready) pods even if there are no disruptions
allowed on a PodDisruptionBudget. This can help to drain/maintain a node and
recover without a manual intervention when multiple instances of nodes or pods
are misbehaving. Use this with caution, as this option can disrupt perspective
pods that have not yet had a chance to become healthy.

Summary by CodeRabbit

  • Chores
    • Updated Pod Disruption Budget configuration to allow unhealthy pods to be evicted according to system disruption policies across package management components.

@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Apr 23, 2026

@atiratree: This pull request references OPRUN-4588 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "5.0.0" version, but no target version was set.

Details

In response to this:

Allow eviction of unhealthy (not ready) pods even if there are no disruptions
allowed on a PodDisruptionBudget. This can help to drain/maintain a node and
recover without a manual intervention when multiple instances of nodes or pods
are misbehaving. Use this with caution, as this option can disrupt perspective
pods that have not yet had a chance to become healthy.

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 openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Apr 23, 2026
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Apr 23, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 62288e3b-9c6b-4a98-baa6-8dbdd2dc45b0

📥 Commits

Reviewing files that changed from the base of the PR and between 122728c and e99debc.

📒 Files selected for processing (3)
  • manifests/0000_50_olm_00-packageserver.pdb.yaml
  • microshift-manifests/0000_50_olm_00-packageserver.pdb.yaml
  • scripts/packageserver-pdb.yaml

Walkthrough

Three PodDisruptionBudget manifest files are updated to add an unhealthyPodEvictionPolicy: AlwaysAllow field to their specifications, enabling the eviction of unhealthy pods according to PDB rules while maintaining existing maxUnavailable and label selector configurations.

Changes

Cohort / File(s) Summary
PodDisruptionBudget Configuration
manifests/0000_50_olm_00-packageserver.pdb.yaml, microshift-manifests/0000_50_olm_00-packageserver.pdb.yaml, scripts/packageserver-pdb.yaml
Added unhealthyPodEvictionPolicy: AlwaysAllow field to packageserver-pdb PodDisruptionBudget spec across all three manifest files.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 12
✅ Passed checks (12 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title directly references the ticket (OPRUN-4588) and clearly describes the main change: enabling AlwaysAllow UnhealthyPodEvictionPolicy in PodDisruptionBudgets, which aligns with the changeset modifications across three manifest files.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names ✅ Passed PR modifies only YAML manifest files defining Kubernetes PodDisruptionBudget resources, not Ginkgo test files.
Test Structure And Quality ✅ Passed PR modifies only YAML manifest files with no test code changes; Ginkgo test quality check is not applicable.
Microshift Test Compatibility ✅ Passed PR only modifies YAML PodDisruptionBudget manifest files and does not add new Ginkgo e2e tests.
Single Node Openshift (Sno) Test Compatibility ✅ Passed PR only modifies Kubernetes YAML manifest files for PodDisruptionBudget resources and does not introduce any new Ginkgo e2e tests.
Topology-Aware Scheduling Compatibility ✅ Passed PodDisruptionBudget uses maxUnavailable: 1, which is topology-appropriate for two-node clusters and compatible with 2-replica deployments. The unhealthyPodEvictionPolicy: AlwaysAllow setting enhances cluster maintenance across all topologies.
Ote Binary Stdout Contract ✅ Passed The OTE Binary Stdout Contract check is not applicable. The PR modifies only Kubernetes YAML manifest files, which are static configuration files, not executable code.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed This PR only modifies YAML manifest files defining Kubernetes PodDisruptionBudget resources. The custom check assesses IPv4 assumptions and external connectivity in Ginkgo e2e tests. Since no Ginkgo e2e tests were added, the check is not applicable.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Comment @coderabbitai help to get the list of available commands and usage tips.

@openshift-ci openshift-ci Bot requested review from anik120 and joelanford April 23, 2026 22:04
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Apr 23, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: atiratree
Once this PR has been reviewed and has the lgtm label, please assign grokspawn 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

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Apr 23, 2026

@atiratree: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/unit-registry e99debc link true /test unit-registry
ci/prow/periodics-images e99debc link true /test periodics-images
ci/prow/e2e-aws-olmv0-ext e99debc link true /test e2e-aws-olmv0-ext
ci/prow/unit-psm e99debc link true /test unit-psm
ci/prow/verify e99debc link true /test verify
ci/prow/unit-api e99debc link true /test unit-api
ci/prow/e2e-gcp-console-olm e99debc link true /test e2e-gcp-console-olm
ci/prow/images e99debc link true /test images
ci/prow/e2e-upgrade e99debc link true /test e2e-upgrade
ci/prow/unit-olm e99debc link true /test unit-olm
ci/prow/e2e-gcp-ovn e99debc link true /test e2e-gcp-ovn
ci/prow/e2e-aws-upgrade-ovn-single-node e99debc link false /test e2e-aws-upgrade-ovn-single-node
ci/prow/e2e-gcp-olm e99debc link true /test e2e-gcp-olm

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants