Skip to content

Commit d8dd20e

Browse files
authored
Merge pull request #52385 from jeana-redhat/OSDOCS-4162-autoscaler-verbosity
[OSDOCS-4162]: Allow setting cluster autoscaler verbosity
2 parents dce36ed + 479c217 commit d8dd20e

File tree

1 file changed

+23
-14
lines changed

1 file changed

+23
-14
lines changed

modules/cluster-autoscaler-cr.adoc

Lines changed: 23 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -33,13 +33,14 @@ spec:
3333
- type: amd.com/gpu
3434
min: 0
3535
max: 4
36-
scaleDown: <10>
37-
enabled: true <11>
38-
delayAfterAdd: 10m <12>
39-
delayAfterDelete: 5m <13>
40-
delayAfterFailure: 30s <14>
41-
unneededTime: 5m <15>
42-
utilizationThreshold: "0.4" <16>
36+
logVerbosity: 4 <10>
37+
scaleDown: <11>
38+
enabled: true <12>
39+
delayAfterAdd: 10m <13>
40+
delayAfterDelete: 5m <14>
41+
delayAfterFailure: 30s <15>
42+
unneededTime: 5m <16>
43+
utilizationThreshold: "0.4" <17>
4344
----
4445
<1> Specify the priority that a pod must exceed to cause the cluster autoscaler to deploy additional nodes. Enter a 32-bit integer value. The `podPriorityThreshold` value is compared to the value of the `PriorityClass` that you assign to each pod.
4546
<2> Specify the maximum number of nodes to deploy. This value is the total number of machines that are deployed in your cluster, not just the ones that the autoscaler controls. Ensure that this value is large enough to account for all of your control plane and compute machines and the total number of replicas that you specify in your `MachineAutoscaler` resources.
@@ -50,13 +51,21 @@ spec:
5051
<7> Optional: Specify the type of GPU node to deploy. Only `nvidia.com/gpu` and `amd.com/gpu` are valid types.
5152
<8> Specify the minimum number of GPUs to deploy in the cluster.
5253
<9> Specify the maximum number of GPUs to deploy in the cluster.
53-
<10> In this section, you can specify the period to wait for each action by using any valid link:https://golang.org/pkg/time/#ParseDuration[ParseDuration] interval, including `ns`, `us`, `ms`, `s`, `m`, and `h`.
54-
<11> Specify whether the cluster autoscaler can remove unnecessary nodes.
55-
<12> Optional: Specify the period to wait before deleting a node after a node has recently been _added_. If you do not specify a value, the default value of `10m` is used.
56-
<13> Optional: Specify the period to wait before deleting a node after a node has recently been _deleted_. If you do not specify a value, the default value of `0s` is used.
57-
<14> Optional: Specify the period to wait before deleting a node after a scale down failure occurred. If you do not specify a value, the default value of `3m` is used.
58-
<15> Optional: Specify the period before an unnecessary node is eligible for deletion. If you do not specify a value, the default value of `10m` is used.
59-
<16> Optional: Specify the _node utilization level_ below which an unnecessary node is eligible for deletion. The node utilization level is the sum of the requested resources divided by the allocated resources for the node, and must be a value greater than `"0"` but less than `"1"`. If you do not specify a value, the cluster autoscaler uses a default value of `"0.5"`, which corresponds to 50% utilization. This value must be expressed as a string.
54+
<10> Specify the logging verbosity level between `0` and `10`. The following log level thresholds are provided for guidance:
55+
+
56+
--
57+
* `1`: (Default) Basic information about changes.
58+
* `4`: Debug-level verbosity for troubleshooting typical issues.
59+
* `9`: Extensive, protocol-level debugging information.
60+
--
61+
+
62+
If you do not specify a value, the default value of `1` is used.
63+
<11> In this section, you can specify the period to wait for each action by using any valid link:https://golang.org/pkg/time/#ParseDuration[ParseDuration] interval, including `ns`, `us`, `ms`, `s`, `m`, and `h`.
64+
<12> Specify whether the cluster autoscaler can remove unnecessary nodes.
65+
<13> Optional: Specify the period to wait before deleting a node after a node has recently been _added_. If you do not specify a value, the default value of `10m` is used.
66+
<14> Optional: Specify the period to wait before deleting a node after a node has recently been _deleted_. If you do not specify a value, the default value of `0s` is used.
67+
<15> Optional: Specify the period to wait before deleting a node after a scale down failure occurred. If you do not specify a value, the default value of `3m` is used.
68+
<16> Optional: Specify the period before an unnecessary node is eligible for deletion. If you do not specify a value, the default value of `10m` is used.<17> Optional: Specify the _node utilization level_ below which an unnecessary node is eligible for deletion. The node utilization level is the sum of the requested resources divided by the allocated resources for the node, and must be a value greater than `"0"` but less than `"1"`. If you do not specify a value, the cluster autoscaler uses a default value of `"0.5"`, which corresponds to 50% utilization. This value must be expressed as a string.
6069
// Might be able to add a formula to show this visually, but need to look into asciidoc math formatting and what our tooling supports.
6170

6271
[NOTE]

0 commit comments

Comments
 (0)