SHA256
1
0
forked from pool/warewulf4
warewulf4/README.RKE2.md
Christian Goll 70b45730b3 - Update to version 4.6.0rc3 what is a major upgrade with following
highlights:
  * renamed container to images
  * "sprig" functions in overlays
  * support for yaml and json formatted output
  * completely re-designed kernel selection support
  * nested profiles
  * arbitrary node and profile data in new "resources" structure
  * moved NFS mount options to resources / fstab overlay
  * split overlays by function
  * split overlays, site vs distribution
  * replaced defaults.conf with settings on default profile
  * improved tabular output
  * parallel overlay build
  * improved networking functionality (static route, vlans, and bonds)
  * kernel arguments as a list
  * non-zero exit codes on wwctl errors
  * fixed argument parsing for wwctl image exec
  * Defined menu for ipxe boot
  * Re-order SSH key types to make ed25519 default.
- The configuation files nodes.conf and warewulf.conf will be updated
  on upgrade and the unmodified configuration files will be saved 
  as nodes.conf.4.5.x and warewulf.conf.4.5.x

OBS-URL: https://build.opensuse.org/package/show/network:cluster/warewulf4?expand=0&rev=99
2025-02-25 18:44:20 +00:00

44 lines
1.3 KiB
Markdown

# RKE2 Cluster Configuration HOWTO
The package warewulf4-overlay-rke2 provides a configuration template
to share a connection token - a shared secret - and the hostname of
the first server endpoint across an RKE2 cluster.
To use it,
- create a profile `rke2-config-key`:
```
wwctl profile add rke2-config-key
token="$(printf 'K'; \
for n in {1..20}; do printf %x $RANDOM; done; \
printf "::server:"; \
for n in {1..20}; do printf %x $RANDOM; done)"
wwctl profile set --tagadd="connectiontoken=${token}" \
-O rke2-config rke2-config-key
```
- create a profile `rke2-config-first-server`:
```
server=<hostname_of_first_rke2_server>
wwctl profile add rke2-config-first-server
wwctl profile set --tagadd="server=${server}" -O rke2-config rke2-config-first-server
```
- add the `rke2-config-key` profile to the server node:
```
wwctl node set -P default,rke2-config-key $server
```
- finally, add both profiles to the agent nodes:
```
agents="<agent_list>"
wwctl node set -P default,rke2-config-key,rke2-config-first-server $agents
```
In case the RKE2 server node is not deployed by Warewulf, you will
have to grab the connection token (see variable `token` above) from
the file `/var/lib/rancher/rke2/server/node-token` on the running
server.