OSDOCS CQA NODES-9: Autoscaling and Miscellaneous III by mburke5678 · Pull Request #112856 · openshift/openshift-docs

mburke5678 · 2026-06-05T11:52:22Z

https://redhat.atlassian.net/browse/OSDOCS-16937

Previews:
Nodes -> Working with pods -> Automatically scaling pods with the horizontal pod autoscaler

Assembly:
'openshift-docs/nodes/pods/nodes-pods-autoscaling.adoc'

openshift-ci-robot · 2026-06-05T11:52:25Z

@mburke5678: No Jira issue with key NODES-9 exists in the tracker at https://redhat.atlassian.net.
Once a valid jira issue is referenced in the title of this pull request, request a refresh with /jira refresh.

Details

In response to this:

https://redhat.atlassian.net/browse/OSDOCS-16937

Assembly:
'openshift-docs/nodes/pods/nodes-pods-autoscaling.adoc'

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.

ocpdocs-previewbot · 2026-06-05T12:07:14Z

🤖 Wed Jun 10 20:02:55 - Prow CI generated the docs preview:

https://112856--ocpdocs-pr.netlify.app/openshift-enterprise/latest/nodes/pods/nodes-pods-autoscaling.html

openshift-ci-robot · 2026-06-05T13:06:26Z

@mburke5678: No Jira issue with key NODES-9 exists in the tracker at https://redhat.atlassian.net.
Once a valid jira issue is referenced in the title of this pull request, request a refresh with /jira refresh.

Details

In response to this:

https://redhat.atlassian.net/browse/OSDOCS-16937

Previews:
Nodes -> Working with pods -> Automatically scaling pods with the horizontal pod autoscaler

Assembly:
'openshift-docs/nodes/pods/nodes-pods-autoscaling.adoc'

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.

jeana-redhat · 2026-06-08T17:01:17Z

The branch/enterprise-5.0 label has been added to this PR.

This is because your PR targets the main branch and is labeled for branch/enterprise-4.22. And any PR going into main must also target the latest version branch (branch/enterprise-5.0).

If the update in your PR does NOT apply to version 5.0 onward, please re-target this PR to go directly into the appropriate enterprise- version branch or branches instead of main.

dfitzmau

Hi, @mburke5678 . Nice work. I've added some minor feedback.

dfitzmau · 2026-06-09T09:17:15Z


-For optimal performance, configure resource requests for all pods. To prevent frequent replica fluctuations, configure the cooldown period.
+[role="_abstract"]
+You can help ensure optimal performance in your cluster by configuring resource requests for all pods and prevent frequent replica fluctuations by configuring the cooldown period.


Suggested change

You can help ensure optimal performance in your cluster by configuring resource requests for all pods and prevent frequent replica fluctuations by configuring the cooldown period.

You can help ensure optimal performance in your cluster by configuring resource requests for all pods. Additionally, you can prevent frequent replica fluctuations by configuring the cooldown period.

Break a large sentence into two.

dfitzmau · 2026-06-09T09:21:35Z

-<4> Specify the target average CPU use over all the pods, represented as a percent of requested CPU. If not specified or negative, a default autoscaling policy is used.
+--
+`<object_type>/<name>`:: Specifies the type and name of the object to autoscale. The object must exist and be a `Deployment`, `DeploymentConfig`/`dc`, `ReplicaSet`/`rs`, `ReplicationController`/`rc`, or `StatefulSet`.
+`min`:: Optional: Specifies the minimum number of replicas when scaling down. Replace <number> with the minimum number of replicas.


Suggested change

`min`:: Optional: Specifies the minimum number of replicas when scaling down. Replace <number> with the minimum number of replicas.

`min`:: Optional parameter. Specifies the minimum number of replicas when scaling down. Replace <number> with the minimum number of replicas.

Where is this rule? I have A LOT of Optional: in the repo. It appears in the doc guidelines.

dfitzmau · 2026-06-09T09:21:44Z

+--
+`<object_type>/<name>`:: Specifies the type and name of the object to autoscale. The object must exist and be a `Deployment`, `DeploymentConfig`/`dc`, `ReplicaSet`/`rs`, `ReplicationController`/`rc`, or `StatefulSet`.
+`min`:: Optional: Specifies the minimum number of replicas when scaling down. Replace <number> with the minimum number of replicas.
+`max`:: Specifies the maximum number of replicas when scaling up. Replace <number> with the maximum number of replicas.


Suggested change

`max`:: Specifies the maximum number of replicas when scaling up. Replace <number> with the maximum number of replicas.

`max`:: Specifies the maximum number of replicas when scaling up. Replace `<number>` with the maximum number of replicas.

dfitzmau · 2026-06-09T09:21:52Z

+`<object_type>/<name>`:: Specifies the type and name of the object to autoscale. The object must exist and be a `Deployment`, `DeploymentConfig`/`dc`, `ReplicaSet`/`rs`, `ReplicationController`/`rc`, or `StatefulSet`.
+`min`:: Optional: Specifies the minimum number of replicas when scaling down. Replace <number> with the minimum number of replicas.
+`max`:: Specifies the maximum number of replicas when scaling up. Replace <number> with the maximum number of replicas.
+`cpu-percent`:: Specifies the target average CPU use over all the pods, represented as a percent of requested CPU. Replace <percent> with requested percentage. If not specified or negative, a default autoscaling policy is used.


Suggested change

`cpu-percent`:: Specifies the target average CPU use over all the pods, represented as a percent of requested CPU. Replace <percent> with requested percentage. If not specified or negative, a default autoscaling policy is used.

`cpu-percent`:: Specifies the target average CPU use over all the pods, represented as a percent of requested CPU. Replace `<percent>` with requested percentage. If not specified or negative, a default autoscaling policy is used.

dfitzmau · 2026-06-09T09:25:09Z

-whether or not the horizontal pod autoscaler (HPA) is able to scale and whether or not it is currently restricted
-in any way.
+[role="_abstract"]
+You can review the horizontal pod autoscaler (HPA) status conditions set to determine whether or not the HPA is able to scale and whether or not it is currently restricted in any way.


openshift-ci · 2026-06-10T20:07:57Z

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

mburke5678 · 2026-06-10T21:11:58Z

/cherrypick enterprise-4.20

mburke5678 · 2026-06-10T21:12:04Z

/cherrypick enterprise-4.22

mburke5678 · 2026-06-10T21:12:12Z

/cherrypick enterprise-4.21

mburke5678 · 2026-06-10T21:12:18Z

/cherrypick enterprise-5.0

openshift-cherrypick-robot · 2026-06-10T21:12:59Z

@mburke5678: new pull request created: #113096

Details

In response to this:

/cherrypick enterprise-4.20

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 · 2026-06-10T21:13:03Z

@mburke5678: new pull request created: #113097

Details

In response to this:

/cherrypick enterprise-4.22

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 · 2026-06-10T21:13:07Z

@mburke5678: new pull request created: #113098

Details

In response to this:

/cherrypick enterprise-4.21

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 · 2026-06-10T21:13:12Z

@mburke5678: new pull request created: #113099

Details

In response to this:

/cherrypick enterprise-5.0

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.

mburke5678 added this to the Continuous Release milestone Jun 5, 2026

mburke5678 added branch/enterprise-4.20 branch/enterprise-4.21 branch/enterprise-4.22 labels Jun 5, 2026

openshift-ci Bot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Jun 5, 2026

mburke5678 force-pushed the cqa-nodes-9-3 branch from ae60df3 to 0da80cf Compare June 5, 2026 13:03

mburke5678 added the merge-review-needed Signifies that the merge review team needs to review this PR label Jun 5, 2026