ClusterAutoscalingProfile interface

Package:

@azure/arm-redhatopenshifthcp

ClusterAutoscaling specifies auto-scaling behavior that applies to all NodePools associated with a control plane.

Properties

maxNodeProvisionTimeSeconds	maxNodeProvisionTimeSeconds is the maximum time to wait for node provisioning before considering the provisioning to be unsuccessful. The default is 900 seconds, or 15 minutes.
maxNodesTotal	maxNodesTotal is the maximum allowable number of nodes. The autoscaler will not grow the cluster beyond this number. If omitted, the autoscaler will not have a maximum limit.
maxPodGracePeriodSeconds	maxPodGracePeriodSeconds is the maximum amount of time in seconds to wait for graceful pod termination before scaling down a NodePool. The default is 600 seconds.
podPriorityThreshold	podPriorityThreshold enables users to schedule "best-effort" pods, which shouldn't trigger autoscaler actions, but only run when there are spare resources available. The default is -10. See the following for more details: https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/FAQ.md#how-does-cluster-autoscaler-work-with-pod-priority-and-preemption

Property Details

maxNodeProvisionTimeSeconds

maxNodeProvisionTimeSeconds is the maximum time to wait for node provisioning before considering the provisioning to be unsuccessful. The default is 900 seconds, or 15 minutes.

maxNodeProvisionTimeSeconds?: number

Property Value

number

maxNodesTotal

maxNodesTotal is the maximum allowable number of nodes. The autoscaler will not grow the cluster beyond this number. If omitted, the autoscaler will not have a maximum limit.

maxNodesTotal?: number

Property Value

number

maxPodGracePeriodSeconds

maxPodGracePeriodSeconds is the maximum amount of time in seconds to wait for graceful pod termination before scaling down a NodePool. The default is 600 seconds.

maxPodGracePeriodSeconds?: number

Property Value

number

podPriorityThreshold

podPriorityThreshold enables users to schedule "best-effort" pods, which shouldn't trigger autoscaler actions, but only run when there are spare resources available. The default is -10. See the following for more details: https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/FAQ.md#how-does-cluster-autoscaler-work-with-pod-priority-and-preemption

podPriorityThreshold?: number

Property Value

number