Skip to content

v1.4.0-dev.0 - preview `add-node` command

Pre-release
Pre-release
Compare
Choose a tag to compare
@iwilltry42 iwilltry42 released this 03 Nov 18:58
v1.4.0-dev.0
9b8fcd1

About

This preview release includes lots of deprecations and code cleanups as well as an experimental new feature to add new nodes to existing clusters.

Preview

  • preview the new k3d add-node command which lets you add new nodes to existing k3d or k3s clusters
    • this is still under development, so you cannot use all the options which are available to the create command yet
NAME:
   k3d add-node - Add nodes to an existing k3d/k3s cluster (k3d by default)

USAGE:
   k3d add-node [command options] [arguments...]

OPTIONS:
   --role value, -r value                              Choose role of the node you want to add [agent|server] (default: "agent")
   --name value, -n value                              Name of the k3d cluster that you want to add a node to [only for node name if --k3s is set] (default: "k3s-default")
   --count value, -c value                             Number of nodes that you want to add (default: 1)
   --image value, -i value                             Specify a k3s image (Format: <repo>/<image>:<tag>) (default: "docker.io/rancher/k3s:v0.10.2")
   --arg value, -x value                               Pass arguments to the k3s server/agent command.
   --env value, -e value                               Pass an additional environment variable (new flag per variable)
   --volume source:destination, -v source:destination  Mount one or more volumes into every created node (Docker notation: source:destination)
   --k3s https://<host>:<port>                         Add a k3d node to a non-k3d k3s cluster (specify k3s server URL like this https://<host>:<port>) [requires k3s-secret or k3s-token]
   --k3s-secret value, -s value                        Specify k3s cluster secret (or use --k3s-token to use a node token)
   --k3s-token value, -t value                         Specify k3s node token (or use --k3s-secret to use a cluster secret)[overrides k3s-secret]

Feedback is very welcome :)
Just releasing this now so you can test it already, since it's going a bit slow at the moment due to high workloads among collaborators.

Assets 8
Loading