chalkctl node renew¶
Issues the node a new node certificate and key from the node CA and delivers them, also once the node's own certificate expired. Such a node is verified by the OS CA as of its certificate's start, so chalkctl trusts the node's old key: someone holding a leaked, expired key of the node and sitting in its network path could receive the new certificate in its place. That is inherent to recovering a node; renewing node certificates before they expire avoids it.
A node revoked with chalkctl node revoke is refused, as is any node while a layer cannot say which nodes are revoked: in a Kubernetes cluster the control planes are asked first, and one whose own certificate expired cannot answer. --force renews without asking. The command needs 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. |
--force |
boolean | false |
Renew without asking whether the node is revoked. |
--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. |
Examples¶
See also¶
- chalkctl node: Manage a node's access, activate its staged image, reboot it and show its diagnostics and routes