Create a cluster
Creates a cluster and starts provisioning. The cluster is returned before provisioning completes.
Returns 400 for, among others: a duplicate cluster name; missing
nico.orgID, siteID or vpcID; an unsupported cniPlugin; a
missing controlPlaneConfig.nico.release; a
control-plane maxSurge greater than 1; a pod CIDR too small for the
requested nodes plus surge; a controlPlaneVIP inside the pod or
service CIDR.
Authentication
A JWT from an issuer the Operator has configured, carried as Authorization: Bearer <token>.
Request
Encrypt etcd at rest. Can be turned on later with enableEtcdEncryption; cannot be turned off.
Virtual IP for the API server through kube-vip. Omit to skip kube-vip and use the first control-plane node’s IP as the API server endpoint. Must not fall inside the pod or service CIDR. An explicit empty string is rejected. Without a VIP, a new cluster must have exactly one desired control-plane node. Control-plane scale-up above one node, upgrades, and configuration changes that replace control-plane nodes require a VIP. Recreate a no-VIP cluster with controlPlaneVIP to make those operations available.
Writable cluster-level control plane configuration supplied at cluster creation.
Required when you create a cluster.
nico carries the NICo settings for the control-plane nodes; it is required
for a NICo cluster. launchLayer is required for a LaunchLayer cluster.
Response
Cluster created; provisioning has started
Desired control-plane Kubernetes version. The running version is in ControlPlaneStatus.
When true, control-plane upgrades and configuration changes replace nodes automatically. When false, nodes needing replacement are reported as pending and wait for an operator.
Current control-plane configuration.