Skip to content

Commit

Permalink
Swagger changes for adding autoscalerprofile flags for daemonset/mult…
Browse files Browse the repository at this point in the history 
…ipleexpander (#25487)

* Adding json changes

* adding "daemonsets" to the custom-words

* Editing "Expander" to "expander"

* Removing daemonset custom word from this pr. look at: #25533
  • Loading branch information
@aagusuab
aagusuab authored Aug 28, 2023
1 parent 7cdd607 commit f58f4e5
Showing 1 changed file with 59 additions and 30 deletions.
89 changes: 59 additions & 30 deletions ...ce-manager/Microsoft.ContainerService/aks/preview/2023-08-02-preview/managedClusters.json
View file
Original file line number Diff line number Diff line change
Expand Up @@ -5228,38 +5228,34 @@
"title": "Detects similar node pools and balances the number of nodes between them.",
"description": "Valid values are 'true' and 'false'"
},
"daemonset-eviction-for-empty-nodes": {
"type": "boolean",
"title": "DaemonSet pods will be gracefully terminated from empty nodes",
"description": "If set to true, all daemonset pods on empty nodes will be evicted before deletion of the node. If the daemonset pod cannot be evicted another node will be chosen for scaling. If set to false, the node will be deleted without ensuring that daemonset pods are deleted or evicted."
},
"daemonset-eviction-for-occupied-nodes": {
"type": "boolean",
"title": "DaemonSet pods will be gracefully terminated from non-empty nodes",
"description": "If set to true, all daemonset pods on occupied nodes will be evicted before deletion of the node. If the daemonset pod cannot be evicted another node will be chosen for scaling. If set to false, the node will be deleted without ensuring that daemonset pods are deleted or evicted."
},
"ignore-daemonsets-utilization": {
"type": "boolean",
"title": "Should CA ignore DaemonSet pods when calculating resource utilization for scaling down",
"description": "If set to true, the resources used by daemonset will be taken into account when making scaling down decisions."
},
"expander": {
"type": "string",
"enum": [
"least-waste",
"most-pods",
"priority",
"random"
],
"x-ms-enum": {
"name": "expander",
"modelAsString": true,
"values": [
{
"value": "least-waste",
"description": "Selects the node group that will have the least idle CPU (if tied, unused memory) after scale-up. This is useful when you have different classes of nodes, for example, high CPU or high memory nodes, and only want to expand those when there are pending pods that need a lot of those resources."
},
{
"value": "most-pods",
"description": "Selects the node group that would be able to schedule the most pods when scaling up. This is useful when you are using nodeSelector to make sure certain pods land on certain nodes. Note that this won't cause the autoscaler to select bigger nodes vs. smaller, as it can add multiple smaller nodes at once."
},
{
"value": "priority",
"description": "Selects the node group that has the highest priority assigned by the user. It's configuration is described in more details [here](https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/expander/priority/readme.md)."
},
{
"value": "random",
"description": "Used when you don't have a particular need for the node groups to scale differently."
}
]
},
"title": "The expander to use when scaling up",
"description": "If not specified, the default is 'random'. See [expanders](https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/FAQ.md#what-are-expanders) for more information."
"title": "Type of node group expander to be used in scale up. Set to be deprecated, please use 'expanders' flag in the future.",
"description": "Available values are: 'least-waste', 'most-pods', 'priority', 'random'.",
"$ref": "#/definitions/expander"
},
"expanders": {
"type": "array",
"title": "Type of node group expander to be used in scale up.",
"description": "Available values are: 'least-waste', 'most-pods', 'priority', 'random'. If multiple expanders are configured, they will be considered in the order in which they are listed, with the first one being considered first.",
"items": {
"$ref": "#/definitions/expander"
}
},
"max-empty-bulk-delete": {
"type": "string",
Expand Down Expand Up @@ -5472,6 +5468,39 @@
}
}
},
"expander": {
"type": "string",
"enum": [
"least-waste",
"most-pods",
"priority",
"random"
],
"x-ms-enum": {
"name": "expander",
"modelAsString": true,
"values": [
{
"value": "least-waste",
"description": "Selects the node group that will have the least idle CPU (if tied, unused memory) after scale-up. This is useful when you have different classes of nodes, for example, high CPU or high memory nodes, and only want to expand those when there are pending pods that need a lot of those resources."
},
{
"value": "most-pods",
"description": "Selects the node group that would be able to schedule the most pods when scaling up. This is useful when you are using nodeSelector to make sure certain pods land on certain nodes. Note that this won't cause the autoscaler to select bigger nodes vs. smaller, as it can add multiple smaller nodes at once."
},
{
"value": "priority",
"description": "Selects the node group that has the highest priority assigned by the user. It's configuration is described in more details [here](https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/expander/priority/readme.md)."
},
{
"value": "random",
"description": "Used when you don't have a particular need for the node groups to scale differently."
}
]
},
"title": "The expander to use when scaling up",
"description": "If not specified, the default is 'random'. See [expanders](https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/FAQ.md#what-are-expanders) for more information."
},
"ManagedClusterAPIServerAccessProfile": {
"type": "object",
"properties": {
Expand Down

0 comments on commit f58f4e5

Please sign in to comment.