yc container cluster create
Статья создана
Обновлена 12 сентября 2025 г.
Create a Kubernetes cluster.
Command Usage
Syntax:
yc container cluster create <CLUSTER-NAME> [Flags...] [Global Flags...]
Flags
| Flag | Description |
|---|---|
--name |
stringName of the Kubernetes cluster. |
--description |
stringNew description for the Kubernetes cluster. |
--network-id |
stringNetwork id. |
--network-name |
stringNetwork name. |
--labels |
key=value[,key=value...]List of Kubernetes cluster labels as key-value pairs. |
--zone |
stringID of the availability zone where the Kubernetes cluster zonal master resides. |
--cluster-ipv4-range |
stringIPv4 range for the Kubernetes cluster pods in CIDR notation. |
--service-ipv4-range |
stringIPv4 range for the Kubernetes cluster services in CIDR notation. |
--cluster-ipv6-range |
stringIPv6 range for the Kubernetes cluster pods in CIDR notation. IPv6 only clusters aren't yet supported, specifying this flag is only valid as a part of a dual IPv4/IPv6 stack cluster creation |
--service-ipv6-range |
stringIPv6 range for the Kubernetes cluster services in CIDR notation. IPv6 only clusters aren't yet supported, specifying this flag is only valid as a part of a dual IPv4/IPv6 stack cluster creation |
--dual-stack |
Create a dual IPv4/IPv6 stack cluster. Specifying this flag will attempt an automatic choice of both IPv4/IPv6 cluster and service CIDRs. |
--node-ipv4-mask-size |
intSize of the masks that are assigned for each node in the cluster. |
--subnet-id |
stringSubnet id. |
--subnet-name |
stringSubnet name. |
--public-ip |
Set when the Kubernetes cluster needs an external IPv4. |
--regional |
Create highly available master for the cluster. Master will be distributed across 3 instances. Equal to --etcd-cluster-size=3 |
--region |
stringID of the region where regional Kubernetes cluster resides |
--master-location |
PROPERTY=VALUE[,PROPERTY=VALUE...]List of regional master locations. Possible property names:
|
--etcd-cluster-size |
intNumber of master instances. Can be equal 1 or 3. |
--release-channel |
stringMaster and Node Groups release channel. Every release channel have it's own list of available versions and new revisions release policy. * 'regular' used by default. It usually have one or two stable kubernetes versions available. It's new revisions contains bug and security fixes, but also can contain new well tested features. * 'rapid' is less stable, but receives new features earlier. Usually have most new kubernetes version available. * 'stable' is most stable, but it's new revisions contains only critical bug and security fixes. |
--version |
stringKubernetes master version. Default depends on release channel. See available in 'yc managed-kubernetes list-versions'. |
--enable-network-policy |
Enable network policy enforcement for the cluster. Calico network policy controller will be used. |
--service-account-id |
stringService account to be used for provisioning Compute and VPC resources for the Kubernetes cluster. |
--service-account-name |
stringService account to be used for provisioning Compute and VPC resources for the Kubernetes cluster. |
--node-service-account-id |
stringService account to be used by the worker nodes of the Kubernetes cluster to access Container Registry or to push node logs and metrics. |
--node-service-account-name |
stringService account to be used by the worker nodes of the Kubernetes cluster to access Container Registry or to push node logs and metrics. |
--auto-upgrade |
Sets auto upgrade maintenance policy. 'true' by default. This policy defines if the master can be upgraded to a new revision in the specified maintenance window. New revisions usually contain security and bug fixes, so it's recommended to leave this policy enabled.Master never upgraded to another major version automatically, even with this policy set to true. Examples: '--auto-upgrade=false', '--auto-upgrade' |
--anytime-maintenance-window |
Allow maintenance anytime. This is default maintenance window. |
--daily-maintenance-window |
PROPERTY=VALUE[,PROPERTY=VALUE...]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: --daily-maintenance-window 'start=22:00,duration=10h --daily-maintenance-window 'start=03:00,duration=8h30m Possible property names:
|
--weekly-maintenance-window |
PROPERTY=VALUE[,PROPERTY=VALUE...]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: --weekly-maintenance-window 'days=[monday,tuesday],start=22:00,duration=10h --weekly-maintenance-window 'days=weekend,start=03:00,duration=8h30m Possible property names:
|
--kms-key-id |
stringKMS key for Kubernetes secrets encryption. |
--kms-key-name |
stringKMS key for Kubernetes secrets encryption. |
--security-group-ids |
value[,value]Security group IDs to use for cluster. |
--master-logging |
PROPERTY=VALUE[,PROPERTY=VALUE...]Configures the logging of Kubernetes master components' logs to Yandex Cloud Logging. Possible property names:
|
--cilium |
PROPERTY=VALUE[,PROPERTY=VALUE...][=] Enable and configure cilium CNI for cluster. Possible property names: |
--master-scale-policy |
PROPERTY=VALUE[,PROPERTY=VALUE...]Enable and configure master scale policy for cluster. Possible property names:
|
--enable-workload-identity-federation |
Enable Workload Identity Federation for cluster. |
--async |
Display information about the operation in progress, without waiting for the operation to complete. |
Global Flags
| Flag | Description |
|---|---|
--profile |
stringSet the custom configuration file. |
--debug |
Debug logging. |
--debug-grpc |
Debug gRPC logging. Very verbose, used for debugging connection problems. |
--no-user-output |
Disable printing user intended output to stderr. |
--retry |
intEnable gRPC retries. By default, retries are enabled with maximum 5 attempts. Pass 0 to disable retries. Pass any negative value for infinite retries. Even infinite retries are capped with 2 minutes timeout. |
--cloud-id |
stringSet the ID of the cloud to use. |
--folder-id |
stringSet the ID of the folder to use. |
--folder-name |
stringSet the name of the folder to use (will be resolved to id). |
--endpoint |
stringSet the Cloud API endpoint (host:port). |
--token |
stringSet the OAuth token to use. |
--impersonate-service-account-id |
stringSet the ID of the service account to impersonate. |
--no-browser |
Disable opening browser for authentication. |
--format |
stringSet the output format: text (default), yaml, json, json-rest. |
--jq |
stringQuery to select values from the response using jq syntax |
-h,--help |
Display help for the command. |