chalkctl bootstrap¶
Initialises the cluster on one control plane: the node starts etcd as its first member, starts the Kubernetes control-plane components and applies chalkos's add-ons and the objects of its Addon documents. chalkctl waits until they are applied, up to --timeout. The node refuses when it is bootstrapped already or holds etcd data, so a second cluster is never initialised; the other control planes join the first. The command needs an admin client file or the secrets file.
Flags¶
| Flag | Type | Default | Description |
|---|---|---|---|
--address |
list of [NODE=]ADDR | each node's address in the inventory | Address of a node's chalkd: host or host:port for the node the command names, or NODE=ADDR for any node; may be repeated. |
--config |
string | $CHALKOSCONFIG, else ~/.config/chalkos/config, unless --secrets is given | Client file to authenticate with instead of the secrets file. |
--identity |
list of string | ~/.config/chalkos/age.key, ~/.ssh/id_ed25519, ~/.ssh/id_rsa | File holding an age identity to decrypt the secrets with; may be repeated. |
--inventory |
string | $CHALKOSINVENTORY, else chalkos.yaml in the current directory, when it exists | Inventory naming the cluster's nodes, their addresses and their config files. |
--secrets |
string | — | Cluster secrets path (.age, .enc.*, or plaintext), provider URI, or - for standard input. |
--timeout |
duration | 20m0s |
How long to wait for the control plane to apply its add-ons and Addon objects. |
Examples¶
See also¶
- chalkctl: Install and operate chalkos clusters