Usage: k3s create [OPTIONS] NAME

  Create a new k3s cluster

Options:
  --control-plane-count INTEGER   The number of control plane nodes
  --worker-count INTEGER          The number of workers
  --metal-address-count INTEGER   The number of floating addresses to route into
                                  the virtual network for metallb to manage.
                                  Ignored if --no-metallb is passed.
  --namespace TEXT                If you are an admin, you can create this
                                  cluster in a different namespace.
  --network TEXT                  Specify a network here to add these nodes to a
                                  pre-existing network. Otherwise one will be
                                  created for this cluster.
  --refresh-version-cache / --no-refresh-version-cache
                                  Force a refresh of the k3s version cache.
  --release-channel TEXT          Select a k3s release channel. Common choices
                                  include stable, latest, and specific versions
                                  pre-pended with a v such as "v1.26".
  --sshkey PATH                   An optional ssh public key to place onto
                                  instances.
  --metallb / --no-metallb        Install metallb for load balancer addresses.
                                  --metal-address-count is ignored when this is
                                  off.
  --longhorn / --no-longhorn      Install longhorn for persistent storage.
  --kubeconfig / --no-kubeconfig  Add the new cluster to your local
                                  ~/.kube/config, merging it into any existing
                                  configuration. Cluster credentials remain
                                  available from 'sf-client k3s getconfig'
                                  either way.
  --manifest PATH                 A local .yaml, .yml or .json manifest to place
                                  in the new cluster's k3s auto-apply directory,
                                  so that k3s applies it when the cluster first
                                  starts. May be repeated. The file is copied
                                  verbatim under its own name: nothing is
                                  templated, and the order manifests are applied
                                  in is k3s's business rather than this
                                  command's.
  --control-plane-cpus INTEGER RANGE
                                  The number of vCPUs for each control plane
                                  node.  [x>=1]
  --control-plane-memory INTEGER RANGE
                                  The memory for each control plane node, in MB.
                                  2048 runs a control plane but does not hold up
                                  under load; 4096 or more is recommended.
                                  [x>=1]
  --control-plane-disk INTEGER RANGE
                                  The disk for each control plane node, in GB.
                                  [x>=1]
  --worker-cpus INTEGER RANGE     The number of vCPUs for each worker node.
                                  [x>=1]
  --worker-memory INTEGER RANGE   The memory for each worker node, in MB.
                                  [x>=1]
  --worker-disk INTEGER RANGE     The disk for each worker node, in GB.  [x>=1]
  --help                          Show this message and exit.
