dcloud eks nodegroups createAdd a node group
The nodes run the cluster’s Kubernetes version and appear in Compute, locked to the node group. nodeRole needs iam:PassRole on that role.
Synopsis
dcloud eks nodegroups create cluster --name name --instance-type instanceType --min-size minSize --desired-size desiredSize --max-size maxSize [flags]Arguments
<cluster>Requiredstring
Also accepted as
--cluster. Constraints: /^(ewk-[0-9a-f]{12}|[a-z]([a-z0-9-]{0,38}[a-z0-9])?)$/
Flags
--nameRequiredstring
Node group name, unique in the cluster (409 when taken): lowercase letters, digits and hyphens, starting with a letter, at most 32 characters
Constraints: /^[a-z]([a-z0-9-]{0,30}[a-z0-9])?$/
--drain-timeout-minutesOptionalnumber
Upgrades: minutes a node’s drain may wait on PodDisruptionBudgets; default 60
Constraints: integer, 5-1440
--force-after-timeoutOptionalboolean (--force-after-timeout / --no-force-after-timeout)
Upgrades: after the timeout, remove the node anyway (true) or pause the upgrade (false, default)
--autoscalingOptionalboolean (--autoscaling / --no-autoscaling)
Let the cluster autoscaler change desiredSize between minSize and maxSize (pending pods grow the group, underused nodes shrink it)
--zonesOptionalarray of string
Availability zones the nodes spread over, balanced (e.g. ["de1a","de1b"]); default the region’s default zone. Applies to nodes created from then on
Constraints: /^[a-z]+[0-9]+[a-z]$/
--instance-typesOptionalarray of string
Instance types to buy, in order, when instanceType is sold out in a zone (same CPU architecture), e.g. performance-8
Constraints: /^[a-z0-9-]{2,24}$/
--capacity-fallbackOptionalobject
Stock fallback; default off. otherZones: zones outside `zones` may be used; equivalentTypes: an equivalent server type may be bought
Constraints: JSON
--instance-typeRequiredstring
An instance type, e.g. performance-4. The provider’s own type names are still accepted, deprecated.
Constraints: 1-32 chars
--labelsOptionalmap of string
Kubernetes labels on every node, e.g. {"workload":"web"}; at most 20. kubernetes.io/, k8s.io/ and eks.ews.cloud/ keys are refused (400). Default none
Constraints: key=value
--taintsOptionalarray of json
Kubernetes taints on every node: { key, value?, effect: NoSchedule | PreferNoSchedule | NoExecute }; at most 10. Default none
--node-roleOptionalstring
Name of an IAM role the nodes act as; needs iam:PassRole on it
Constraints: 1-128 chars
--tagsOptionalmap of string
Tags for the new resource, e.g. {"env": "prod", "project": "shop"}. Keys your organization marks required must be present, or the create is refused with the missing keys (GET /tags/api/keys lists them).
Constraints: key=value
--min-sizeRequirednumber
Fewest nodes, 0–100; the cluster autoscaler never goes below it. minSize ≤ desiredSize ≤ maxSize, else 400
Constraints: integer, 0-100
--desired-sizeRequirednumber
Nodes to run now, 0–100; with autoscaling on, the cluster autoscaler changes it between minSize and maxSize
Constraints: integer, 0-100
--max-sizeRequirednumber
Most nodes, 1–100; what the quotas count (nodes per node group, and nodes per cluster summed over its node groups; 20 and 50 by default): 409 QuotaExceeded above them
Constraints: integer, 1-100
Example
dcloud eks nodegroups create cluster --name example --instance-type example --min-size 1 --desired-size 1 --max-size 1Generated from the API description, the same one the API checks requests against and the CLI is built from.