yc managed-kubernetes node-group update
Modify configuration or attributes of a node group.
Command Usage
Syntax:
yc managed-kubernetes node-group update <NODE-GROUP-NAME>|<NODE-GROUP-ID> [Flags...] [Global Flags...]
Flags
|
Flag |
Description |
|
|
ID of the node group. |
|
|
Name of the node group. |
|
|
Display information about the operation in progress, without waiting for the operation to complete. |
|
|
New name of the node group. |
|
|
New description for the node group. |
|
|
List of node group labels as key-value pairs. |
|
|
List of node group NODE labels as key-value pairs. |
|
|
Metadata for instances in the node group. |
|
|
Same as --metadata except that the value for the entry will be read from a local file. |
|
|
New list of platform (not Kubernetes) labels for Compute Cloud instances in the node group as key-value pairs. Existing list of labels will be completely overwritten. |
|
|
Same as --template-labels except that the list of key-value pairs for the entry will be read from a local file. |
|
|
Specifies platform for instances in the node group. |
|
|
Specifies how much memory instances should have. |
|
|
Specifies how many CPU cores instances should have. |
|
|
Specifies baseline performance for a core in percent. |
|
|
Specifies how many GPUs instances should have. |
|
|
Specifies the type of the disk to create. |
|
|
Specifies the size of the disk. |
|
|
Specifies if created nodes will be preemptible. |
|
|
Specifies fixed scale policy size. |
|
|
Auto scale policy for Node Group. Possible property names:
|
|
|
List of node group locations. Possible property names:
|
|
|
Node Kubernetes components version. See available in 'yc managed-kubernetes list-versions'. |
|
|
Update nodes to latest available revision of current version. NodeGroup.version_info.new_revision_available should be true. |
|
|
Sets auto upgrade maintenance policy. |
|
|
Sets auto repair maintenance policy. |
|
|
Allow maintenance anytime. This is default maintenance window. |
|
|
Allow maintenance everyday specified days of week in the specified time window. Flag can be used multiple times, to define different time windows for different days of week. Examples:
Possible property names:
|
|
|
Allow maintenance on specified days of week in the specified time window. Flag can be used multiple times, to define different time windows for different days of week. Examples:
Possible property names:
|
|
|
Number of extra nodes to be created on each update of the node group. |
|
|
Number of nodes that can be unavailable at the same time on each update of the node group. |
|
|
Update network interfaces for the node group. Possible property names:
|
|
|
Update name of the node. |
|
|
Type of a network acceleration for nodes. Values: 'standard', 'software-accelerated' |
|
|
Type of a container runtime settings for nodes. Values: 'docker', 'containerd' |
Global Flags
|
Flag |
Description |
|
|
Set the custom configuration file. |
|
|
Debug logging. |
|
|
Debug gRPC logging. Very verbose, used for debugging connection problems. |
|
|
Disable printing user intended output to stderr. |
|
|
Enable gRPC retries. By default, retries are enabled with maximum 5 attempts. |
|
|
Set the ID of the cloud to use. |
|
|
Set the ID of the folder to use. |
|
|
Set the name of the folder to use (will be resolved to id). |
|
|
Set the Cloud API endpoint (host:port). |
|
|
Set the OAuth token to use. |
|
|
Set the ID of the service account to impersonate. |
|
|
Disable opening browser for authentication. |
|
|
Set the output format: text (default), yaml, json, json-rest. |
|
|
Query to select values from the response using jq syntax |
|
|
Display help for the command. |