Skip to content

[release-v0.25] fix: Do not create PodDisruptionBudget for single replica topology mode - #1715

Merged
kubevirt-bot merged 1 commit into
kubevirt:release-v0.25from
kubevirt-bot:cherry-pick-1707-to-release-v0.25
Mar 17, 2026
Merged

[release-v0.25] fix: Do not create PodDisruptionBudget for single replica topology mode#1715
kubevirt-bot merged 1 commit into
kubevirt:release-v0.25from
kubevirt-bot:cherry-pick-1707-to-release-v0.25

Conversation

@kubevirt-bot

Copy link
Copy Markdown
Contributor

This is an automated cherry-pick of #1707

/assign akrejcir

None

The PodDisruptionBudget does not make sense in single replica topology
mode. It would have "spec.minAvailable" set to 1, but there would always
be one pod. It would cause a warning to be always present:

"The pod disruption budget is at the minimum disruptions allowed level.
The number of current healthy pods is equal to the desired healthy
pods."

Assisted-by: Claude <noreply@anthropic.com>
Signed-off-by: Andrej Krejcir <akrejcir@redhat.com>
@kubevirt-bot kubevirt-bot added release-note-none Denotes a PR that doesn't merit a release note. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. labels Mar 17, 2026
@kubevirt-bot
kubevirt-bot requested review from 0xFelix and ksimon1 March 17, 2026 15:10
@sonarqubecloud

Copy link
Copy Markdown

Quality Gate Failed Quality Gate failed

Failed conditions
10.2% Duplication on New Code (required ≤ 3%)

See analysis details on SonarQube Cloud

@0xFelix 0xFelix 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.

/approve

@kubevirt-bot

Copy link
Copy Markdown
Contributor Author

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: 0xFelix

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

@kubevirt-bot kubevirt-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 17, 2026
@jcanocan

Copy link
Copy Markdown
Contributor

/lgtm

@kubevirt-bot kubevirt-bot added the lgtm Indicates that a PR is ready to be merged. label Mar 17, 2026
@kubevirt-bot
kubevirt-bot merged commit b17b1b2 into kubevirt:release-v0.25 Mar 17, 2026
11 checks passed
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. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. lgtm Indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesn't merit a release note. size/M

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants