Skip to content

OSDOCS-14810:Removed 'at least' wording for control plane and infra nodes in ROSA Classic cluster failure doc. #95079

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 1 commit into from
Jun 30, 2025
Merged

OSDOCS-14810:Removed 'at least' wording for control plane and infra nodes in ROSA Classic cluster failure doc. #95079

merged 1 commit into from
Jun 30, 2025

Conversation

AedinC
Copy link
Contributor

@AedinC AedinC commented Jun 23, 2025 •
edited
Loading

Version(s):
4.19+

Issue:
https://issues.redhat.com/browse/OSDOCS-14810

Link to docs preview:
Cluster failure

Peer review:

  • Peer reviewer has approved this change.

SME review:

  • SME has approved this change.

QE review:
QE approval is not required as no update to procedural information.

Additional information:

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jun 23, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jun 23, 2025 •
edited by openshift-ci bot
Loading

@AedinC: This pull request references OSDOCS-14810 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 bug to target the "4.20.0" version, but no target version was set.

In response to this:

Version(s):
4.19+

Issue:
https://issues.redhat.com/browse/OSDOCS-14810

Link to docs preview:

Peer review:

  • Peer reviewer has approved this change.

SME review:

  • SME has approved this change.

QE review:
QE approval is not required as no update to procedural information.

Additional information:

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 openshift-ci bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Jun 23, 2025
@ocpdocs-previewbot
Copy link

ocpdocs-previewbot commented Jun 23, 2025 •
edited
Loading

🤖 Fri Jun 27 08:15:36 - Prow CI generated the docs preview:

https://95079--ocpdocs-pr.netlify.app/openshift-rosa-hcp/latest/rosa_architecture/rosa_policy_service_definition/rosa-policy-understand-availability.html
https://95079--ocpdocs-pr.netlify.app/openshift-rosa/latest/rosa_architecture/rosa_policy_service_definition/rosa-policy-understand-availability.html

@openshift-ci-robot
Copy link

openshift-ci-robot commented Jun 23, 2025 •
edited by openshift-ci bot
Loading

@AedinC: This pull request references OSDOCS-14810 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 bug to target the "4.20.0" version, but no target version was set.

In response to this:

Version(s):
4.19+

Issue:
https://issues.redhat.com/browse/OSDOCS-14810

Link to docs preview:
Cluster failure

Peer review:

  • Peer reviewer has approved this change.

SME review:

  • SME has approved this change.

QE review:
QE approval is not required as no update to procedural information.

Additional information:

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.

mletalie
mletalie reviewed Jun 23, 2025
View reviewed changes
Copy link
Contributor

@mletalie mletalie left a comment

Choose a reason for hiding this comment

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

/label peer-review-in-progress

@openshift-ci openshift-ci bot added the peer-review-in-progress Signifies that the peer review team is reviewing this PR label Jun 23, 2025
mletalie
mletalie reviewed Jun 23, 2025
View reviewed changes
Copy link
Contributor

@mletalie mletalie left a comment

Choose a reason for hiding this comment

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

/label peer-review-done
/remove-label peer-review-in-progress
/lgtm

@openshift-ci openshift-ci bot added peer-review-done Signifies that the peer review team has reviewed this PR and removed peer-review-in-progress Signifies that the peer review team is reviewing this PR labels Jun 23, 2025
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jun 23, 2025
@AedinC
Copy link
Contributor Author

AedinC commented Jun 23, 2025

Hi @fahlmant. I have double checked that there are 2 infra nodes for single-az clusters and 3 for multi-az. Is there anything else that needs to be changed here? Thanks.

@AedinC
Copy link
Contributor Author

AedinC commented Jun 24, 2025

@arendej Can you please give a LGTM to this? Many thanks.

fahlmant
fahlmant reviewed Jun 26, 2025
View reviewed changes
modules/rosa-policy-failure-points.adoc Outdated

Multi-AZ ROSA clusters have at least three control plane nodes and three infrastructure nodes that are preconfigured for high availability, either in a single zone or across multiple zones, depending on the type of cluster you have selected. Control plane and infrastructure nodes have the same resiliency as worker nodes, with the added benefit of being managed completely by Red{nbsp}Hat.
Multi-AZ ROSA clusters have three control plane nodes and three infrastructure nodes that are preconfigured for high availability, either in a single zone or across multiple zones, depending on the type of cluster you have selected. Control plane and infrastructure nodes have the same resiliency as worker nodes, with the added benefit of being managed completely by Red{nbsp}Hat.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
Multi-AZ ROSA clusters have three control plane nodes and three infrastructure nodes that are preconfigured for high availability, either in a single zone or across multiple zones, depending on the type of cluster you have selected. Control plane and infrastructure nodes have the same resiliency as worker nodes, with the added benefit of being managed completely by Red{nbsp}Hat.
Multi-AZ ROSA clusters have three control plane nodes and three infrastructure nodes that are preconfigured for high availability, one in each Availability Zone. Control plane and infrastructure nodes have the same resiliency as worker nodes, with the added benefit of being managed completely by Red{nbsp}Hat.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Thanks @fahlmant.

@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Jun 27, 2025
@openshift-ci OpenShift CI
Copy link

openshift-ci bot commented Jun 27, 2025

New changes are detected. LGTM label has been removed.

@openshift-ci OpenShift CI
Copy link

openshift-ci bot commented Jun 27, 2025

@AedinC: all tests passed!

Full PR test history. Your PR dashboard.

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-ci-robot
Copy link

openshift-ci-robot commented Jun 27, 2025 •
edited by openshift-ci bot
Loading

@AedinC: This pull request references OSDOCS-14810 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 bug to target the "4.20.0" version, but no target version was set.

In response to this:

Version(s):
4.19+

Issue:
https://issues.redhat.com/browse/OSDOCS-14810

Link to docs preview:
Cluster failure

Peer review:

  • Peer reviewer has approved this change.

SME review:

  • SME has approved this change.

QE review:
QE approval is not required as no update to procedural information.

Additional information:

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.

fahlmant
fahlmant approved these changes Jun 27, 2025
View reviewed changes
Copy link
Contributor

@fahlmant fahlmant left a comment

Choose a reason for hiding this comment

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

lgtm

@openshift-ci-robot
Copy link

openshift-ci-robot commented Jun 27, 2025 •
edited by openshift-ci bot
Loading

@AedinC: This pull request references OSDOCS-14810 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 bug to target the "4.20.0" version, but no target version was set.

In response to this:

Version(s):
4.19+

Issue:
https://issues.redhat.com/browse/OSDOCS-14810

Link to docs preview:
Cluster failure

Peer review:

  • Peer reviewer has approved this change.

SME review:

  • SME has approved this change.

QE review:
QE approval is not required as no update to procedural information.

Additional information:

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.

@AedinC
Copy link
Contributor Author

AedinC commented Jun 30, 2025

/label mergre-review-needed

@openshift-ci OpenShift CI
Copy link

openshift-ci bot commented Jun 30, 2025

@AedinC: The label(s) /label mergre-review-needed cannot be applied. These labels are supported: acknowledge-critical-fixes-only, platform/aws, platform/azure, platform/baremetal, platform/google, platform/libvirt, platform/openstack, ga, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, px-approved, docs-approved, qe-approved, ux-approved, no-qe, downstream-change-needed, rebase/manual, cluster-config-api-changed, approved, backport-risk-assessed, bugzilla/valid-bug, cherry-pick-approved, cloud-experts, cnv, dev-tools, distributed-tracing, ims, jira/valid-bug, merge-review-in-progress, merge-review-needed, mtc, multi-arch, oadp, peer-review-done, peer-review-in-progress, peer-review-needed, rhacs, rhv, sd-docs, serverless, service-mesh, sme-review-done, sme-review-needed, stability-fix-approved, staff-eng-approved, telco. Is this label configured under labels -> additional_labels or labels -> restricted_labels in plugin.yaml?

In response to this:

/label mergre-review-needed

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.

@AedinC
Copy link
Contributor Author

AedinC commented Jun 30, 2025

/label merge-review-needed

@openshift-ci openshift-ci bot added the merge-review-needed Signifies that the merge review team needs to review this PR label Jun 30, 2025
@JoeAldinger JoeAldinger self-assigned this Jun 30, 2025
@JoeAldinger JoeAldinger added merge-review-in-progress Signifies that the merge review team is reviewing this PR and removed merge-review-needed Signifies that the merge review team needs to review this PR labels Jun 30, 2025
@JoeAldinger JoeAldinger added this to the Continuous Release milestone Jun 30, 2025
@JoeAldinger JoeAldinger merged commit c4219ed into openshift:main Jun 30, 2025
2 checks passed
@JoeAldinger
Copy link
Contributor

/cherrypick enterprise-4.20
/cherrypick enterprise-4.19

@openshift-cherrypick-robot
Copy link

@JoeAldinger: new pull request created: #95453

In response to this:

/cherrypick enterprise-4.20
/cherrypick enterprise-4.19

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.

@openshift-cherrypick-robot openshift-cherrypick-robot mentioned this pull request Jun 30, 2025
Merged
@openshift-cherrypick-robot
Copy link

@JoeAldinger: new pull request created: #95454

In response to this:

/cherrypick enterprise-4.20
/cherrypick enterprise-4.19

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.

@openshift-cherrypick-robot openshift-cherrypick-robot mentioned this pull request Jun 30, 2025
Merged
@JoeAldinger JoeAldinger removed their assignment Jun 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@mletalie mletalie mletalie left review comments

@fahlmant fahlmant fahlmant approved these changes

Assignees

@mletalie mletalie

Labels
branch/enterprise-4.19 branch/enterprise-4.20 jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. merge-review-in-progress Signifies that the merge review team is reviewing this PR peer-review-done Signifies that the peer review team has reviewed this PR size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Milestone
Continuous Release
Development

Successfully merging this pull request may close these issues.
7 participants
@AedinC @openshift-ci-robot @ocpdocs-previewbot @JoeAldinger @openshift-cherrypick-robot @fahlmant @mletalie