Skip to content

OCPBUGS-114888: Updated exactly three control plane nodes must be to m… - #119021

Open
dfitzmau wants to merge 1 commit into
openshift:mainfrom
dfitzmau:OCPBUGS-114888
Open

OCPBUGS-114888: Updated exactly three control plane nodes must be to m…#119021
dfitzmau wants to merge 1 commit into
openshift:mainfrom
dfitzmau:OCPBUGS-114888

Conversation

@dfitzmau

@dfitzmau dfitzmau commented Aug 31, 2026

Copy link
Copy Markdown
Contributor

@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Aug 31, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@dfitzmau: This pull request references Jira Issue OCPBUGS-114888, which is invalid:

  • expected the bug to target the "5.1.0" version, but no target version was set
  • expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is MODIFIED instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Version(s):

Issue:
OSDOCS-20272

Link to docs preview:

  • SME has approved this change.
  • QE has approved this change.

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.

@dfitzmau dfitzmau changed the title OCPBUGS-114888: UPdated xactly three control plane nodes must be to m… OCPBUGS-114888: Updated exactly three control plane nodes must be to m… Aug 31, 2026
@openshift-ci openshift-ci Bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Aug 31, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@dfitzmau: This pull request references Jira Issue OCPBUGS-114888, which is invalid:

  • expected the bug to target the "5.1.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Version(s):
4.17+

Issue:
OSDOCS-20272

Link to docs preview:

  • SME has approved this change.
  • QE has approved this change.

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.

Comment thread modules/architecture-machine-roles.adoc
@openshift-ci

openshift-ci Bot commented Aug 31, 2026

Copy link
Copy Markdown

@dfitzmau: 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.

@agawai

agawai commented Aug 31, 2026

Copy link
Copy Markdown

LGTM

@sandeepknd

Copy link
Copy Markdown

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Aug 31, 2026
====
ifndef::openshift-dedicated,openshift-rosa[]
Exactly three control plane nodes must be used for all production deployments. However, on bare metal platforms, clusters can be scaled up to five control plane nodes.
Exactly three control plane nodes must be used for all production deployments. On a bare-metal platform, you can scale a cluster to three, four, or five control plane nodes.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The etcd cluster size must be odd. Even cluster sizes like 4 have a worse fault tolerance than 3 since more nodes can fail to get us to quorum loss.
https://etcd.io/docs/v3.7/faq/#why-an-odd-number-of-cluster-members

So we should only recommend odd sizes: 3 and 5.

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

Labels

branch/enterprise-4.17 branch/enterprise-4.18 branch/enterprise-4.19 branch/enterprise-4.20 branch/enterprise-4.21 branch/enterprise-4.22 branch/enterprise-5.0 jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. 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. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants