Skip to content

Conversation

kquinn1204
Copy link
Contributor

@kquinn1204 kquinn1204 commented Oct 8, 2025

[TELCODOCS-2270]: topology-aware scheduler: HA by default

Version(s): 4.20

Issue: https://issues.redhat.com/browse/TELCODOCS-2270

Link to docs preview: https://100184--ocpdocs-pr.netlify.app/openshift-enterprise/latest/release_notes/ocp-4-20-release-notes.html#ocp-release-notes-numa-resources-operator-replicas_release-notes

QE review:

  • QE has approved this change.

Additional information:

@openshift-ci openshift-ci bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Oct 8, 2025
@kquinn1204 kquinn1204 force-pushed the TELCODOCS-2270-RN-update branch from e5441a6 to 617db30 Compare October 8, 2025 10:45
@ocpdocs-previewbot
Copy link

ocpdocs-previewbot commented Oct 8, 2025

🤖 Wed Oct 08 11:15:49 - Prow CI generated the docs preview:

https://100184--ocpdocs-pr.netlify.app/openshift-enterprise/latest/release_notes/ocp-4-20-release-notes.html

@kquinn1204 kquinn1204 force-pushed the TELCODOCS-2270-RN-update branch from ed73d03 to f42871b Compare October 8, 2025 10:55
==== Configuring NUMA-aware scheduler replicas and high availability (Technology Preview)

In {product-title} {product-version}, the NUMA Resources Operator automatically enables high availability (HA) mode by default. In this mode, the NUMA Resources Operator creates one scheduler replica for each control-plane node in the cluster to ensure redundancy. This default behavior occurs if the `spec.replicas` field is not specified in the `NUMAResourcesScheduler` Custom Resource (CR). Alternatively, you can explicitly set a specific number of scheduler replicas to override the default HA behavior or disable the scheduler entirely by setting the `spec.replicas` field to `0`.
In {product-title} {product-version}, the NUMA Resources Operator automatically enables high availability (HA) mode by default. In this mode, the NUMA Resources Operator creates one scheduler replica for each control-plane node in the cluster to ensure redundancy. This default behavior occurs if the `spec.replicas` field is not specified in the `NUMAResourcesScheduler` Custom Resource (CR). Alternatively, you can explicitly set a specific number of scheduler replicas to override the default HA behavior or disable the scheduler entirely by setting the `spec.replicas` field to `0`. The maximum number of replicas is 3, even if the number of control plane nodes exceeds 3.
Copy link
Collaborator

Choose a reason for hiding this comment

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

🤖 [error] Vale.Terms: Use 'custom resources?' instead of 'Custom Resource'.

Copy link

openshift-ci bot commented Oct 8, 2025

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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.

3 participants