Compute nodes provisioned by Warewulf are stateless. They boot from an image served over the network, so anything a node writes to its root filesystem at runtime, including the result of ipa-client-install, is gone on the next reboot. Enrolling a node by hand works until it restarts. To keep nodes enrolled, the enrollment has to live on the Warewulf server and reach each node at boot.
Warewulf Pro's warewulf-overlays-sssd package does this for Active Directory, FreeIPA, and plain LDAP. For FreeIPA it uses two overlays:
* sssd, a system overlay that configures SSSD and Kerberos on each node and delivers the IPA CA certificate
* krb5.keytab, a runtime overlay that delivers each node's host keytab from the Warewulf server
Each node gets its own IPA host entry and keytab, created once on the Warewulf server. Nodes never run ipa-client-install.
This guide assumes Warewulf Pro 4.7 with at least one node booting a Rocky Linux 9 image, and that the Warewulf server and the nodes can resolve and reach your IPA servers through DNS. The examples use the IPA domain example.com, the IPA server ipa.example.com, and a node named n1 at 10.0.2.1.
Enroll the Warewulf server
The Warewulf server itself should be an IPA client. If it isn't already, enroll it with ipa-client-install. That gives you the ipa and ipa-getkeytab tools used below, and puts the IPA CA certificate at /etc/ipa/ca.crt, which the overlay passes on to the nodes. It also lets the server resolve IPA users, which comes in handy for home directories.
Prepare the node image
The image needs the SSSD and IPA client packages, with SSSD selected as the authentication profile. The cleanest way to get that is a Containerfile. It keeps the image definition version-controlled and reproducible:
FROM ghcr.io/warewulf/warewulf-rockylinux:9
RUN dnf \-y install sssd sssd-ipa krb5-workstation authselect \\
&& authselect select sssd \--force \\
&& systemctl enable sssd \\
&& dnf clean all
Save it as Containerfile in its own directory, then build it there and import it into Warewulf:
\[root@wwctl \~\]\# podman build . \--file Containerfile \--tag rockylinux-9-ipa
\[root@wwctl \~\]\# wwctl image import \$(podman image mount localhost/rockylinux-9-ipa) rockylinux-9-ipa
\[root@wwctl \~\]\# podman image unmount localhost/rockylinux-9-ipa
\[root@wwctl \~\]\# wwctl image build rockylinux-9-ipa
Assign the image to your nodes with --image rockylinux-9-ipa. If you'd rather add the packages to an image you already have:
\[root@wwctl \~\]\# wwctl image shell rockylinux-9
\[rockylinux-9\] Warewulf\> dnf install \-y sssd sssd-ipa krb5-workstation authselect
\[rockylinux-9\] Warewulf\> authselect select sssd \--force
\[rockylinux-9\] Warewulf\> systemctl enable sssd
\[rockylinux-9\] Warewulf\> exit
Keep authselect in that list. Not every Warewulf node image includes it.
Turn on secure mode
A host keytab is a credential. Anyone holding a node's keytab can authenticate to IPA as that node. By default, Warewulf serves overlays to anyone on the provisioning network who asks, so turn on secure mode in /etc/warewulf/warewulf.conf first:
warewulf:
secure: true
With secure mode on, Warewulf serves the runtime overlay only to requests from a privileged port, which means only root on the node can fetch it. That's why the keytab lives in a runtime overlay and not a system overlay. Restart warewulfd, then rebuild overlays and reboot the nodes so wwclient switches to a privileged port:
\[root@wwctl \~\]\# systemctl restart warewulfd
\[root@wwctl \~\]\# wwctl overlay build
Create a host and keytab for each node
As root on the Warewulf server, authenticate as an IPA administrator, add a host for the node, and pull its keytab:
\[root@wwctl \~\]\# kinit admin
\[root@wwctl \~\]\# install \-d \-m 0700 /etc/warewulf/keytabs
\[root@wwctl \~\]\# ipa host-add n1.example.com \--ip-address=10.0.2.1
\[root@wwctl \~\]\# ipa-getkeytab \-s ipa.example.com \-p host/n1.example.com \-k /etc/warewulf/keytabs/n1.keytab
\[root@wwctl \~\]\# base64 \-w0 /etc/warewulf/keytabs/n1.keytab \> /etc/warewulf/keytabs/n1.keytab.b64
\[root@wwctl \~\]\# chmod 0600 /etc/warewulf/keytabs/n1.keytab\*
\[root@wwctl \~\]\# kdestroy
If IPA manages your DNS, --ip-address creates the node's A record at the same time. If IPA doesn't manage the reverse zone, you'll see a warning that the reverse DNS update failed. The host is still added.
The IPA host name needs to be the Warewulf node name followed by the domain, n1.example.com here. If your node hosts live in a different DNS domain than the IPA domain, set the sssd_host_domain tag to that domain.
The overlay reads the base64 copy, named after the node. Warewulf's template Include function strips a trailing newline byte, so a raw keytab that happened to end in 0x0a would arrive corrupted. Base64 sidesteps that.
If you're setting up several nodes, run the host and keytab steps in a loop under the same kinit admin ticket. This loop reads each node's IP address from Warewulf:
\[root@wwctl \~\]\# kinit admin
\[root@wwctl \~\]\# for n in n{1..100}; do
ip=\$(wwctl node list \-n \$n \| awk 'NR\>2 {print \$4; exit}')
ipa host-add \$n.example.com \--ip-address=\$ip
ipa-getkeytab \-s ipa.example.com \-p host/\$n.example.com \-k /etc/warewulf/keytabs/\$n.keytab
base64 \-w0 /etc/warewulf/keytabs/\$n.keytab \> /etc/warewulf/keytabs/\$n.keytab.b64
done
\[root@wwctl \~\]\# chmod 0600 /etc/warewulf/keytabs/\*
\[root@wwctl \~\]\# kdestroy
Replace n{1..100} with your node names.
Configure the overlays
Install the package, put the two overlays in their own profile, and tell it your domain and that it's talking to IPA:
\[root@wwctl \~\]\# dnf install \-y warewulf-overlays-sssd
\[root@wwctl \~\]\# wwctl profile add ipa
\[root@wwctl \~\]\# wwctl profile set ipa \\
\--system-overlays sssd \\
\--runtime-overlays krb5.keytab \\
\--tagadd sssd\_domain=example.com \\
\--tagadd sssd\_provider=ipa
\[root@wwctl \~\]\# wwctl node set n1 \--profile default,ipa
\[root@wwctl \~\]\# wwctl overlay build
Overlays from multiple profiles are combined on each node, so this leaves your default profile alone.
With sssd_provider=ipa, SSSD finds the IPA servers through DNS, users log in with short names, and home directories default to /home/<user> when IPA doesn't specify one. To pin specific servers, set sssd_server. To see every tag, run:
\[root@wwctl \~\]\# wwctl overlay info sssd etc/sssd/sssd.conf.ww
To check what a node will get before rebooting it:
\[root@wwctl \~\]\# wwctl overlay show \-r n1 sssd /etc/sssd/sssd.conf.ww
Boot and verify
\[root@wwctl \~\]\# wwctl power cycle n1
\[root@wwctl \~\]\# ssh n1
\[root@n1 \~\]\# kinit \-k host/n1.example.com && klist && kdestroy
\[root@n1 \~\]\# getent passwd user
\[root@n1 \~\]\# id user
The kinit -k line confirms the node can authenticate to IPA with its own host keytab. IPA assigns POSIX IDs itself, so id shows the same UID and GID on every node and every other IPA client. After that, log in over SSH as an IPA user, reboot the node, and check again. Nothing needs to be redone after a reboot.
Access is controlled by IPA's host-based access control rules, the same as for any other IPA client. Out of the box, the allow_all rule lets every user log in to every host. If you've replaced it with something stricter, add a rule for your compute nodes.
One small thing you may notice: IPA gives new users /bin/sh as their login shell unless you change the default. ipa config-mod --defaultshell=/bin/bash changes it for users created afterwards.
Home directories
Compute nodes often can't create home directories themselves. Warewulf's default profile mounts /home over NFS from the Warewulf server, exported with root_squash, so root on a node can't write there. That's a sensible default. Leave it alone and create each user's home directory on the system that hosts /home (the Warewulf server, with the default profile) before their first login. Without it, the login fails with "Could not chdir to home directory".
Because the Warewulf server is an IPA client, it resolves IPA users by name, and mkhomedir_helper creates the directory from /etc/skel with the right owner, mode, and SELinux context:
\[root@wwctl \~\]\# mkhomedir\_helper user 0077
Tip: If /home is local to each node, or the nodes can write to it as root, they can create home directories at first login instead: add oddjob-mkhomedir to the image, use authselect select sssd with-mkhomedir --force, and enable oddjobd. On a stateless node, a local /home lives in memory and is cleared on every reboot unless a local disk is mounted there.
Rotating host keys
To replace a node's host keys, pull a new keytab on the Warewulf server and push it out:
\[root@wwctl \~\]\# kinit admin
\[root@wwctl \~\]\# ipa-getkeytab \-s ipa.example.com \-p host/n1.example.com \-k /etc/warewulf/keytabs/n1.keytab
\[root@wwctl \~\]\# base64 \-w0 /etc/warewulf/keytabs/n1.keytab \> /etc/warewulf/keytabs/n1.keytab.b64
\[root@wwctl \~\]\# wwctl overlay build n1
\[root@wwctl \~\]\# kdestroy
ipa-getkeytab generates new keys, and the node's old keys stop working as soon as it runs, so don't skip the overlay build. Warewulf rebuilds overlays when overlay files change, but it doesn't notice changes to the keytab files the overlay reads. Once the overlay is rebuilt, the running node picks up the new keytab within a minute, with no reboot.
Tip: until the new keytab arrives, the node still holds the old one, which IPA no longer accepts, so logins on that node can fail for up to a minute. To deliver it right away, have wwclient on the node pull its overlays now:
\[root@wwctl \~\]\# wwctl ssh n1 systemctl reload wwclient
To rotate automatically, use warewulf-krb5-rotate, which the package installs. It runs the steps above for you, and each node authenticates with its own keytab, so no administrator credentials are stored on the Warewulf server. It keeps the newest two key versions in each keytab. To rotate nodes now:
\[root@wwctl \~\]\# warewulf-krb5-rotate \--reload n1 n2
To rotate on a schedule, tag the nodes and enable the timer. Once a day, it rotates each tagged node whose keytab file is older than krb5_rotate_days (30 by default), rebuilds its overlays, and reloads wwclient on it. This example sets a 90-day period; leave out the krb5_rotate_days tag to keep the default:
\[root@wwctl \~\]\# wwctl profile set ipa \--tagadd krb5\_rotate=true \--tagadd krb5\_rotate\_days=90
\[root@wwctl \~\]\# systemctl enable \--now warewulf-krb5-rotate.timer
Adding nodes
For each new node, run the ipa host-add, ipa-getkeytab, and base64 steps with that node's name, add it to the ipa profile, and run wwctl overlay build.
The full setup guide, including every supported tag, is in the Warewulf Pro training curriculum under Pro overlays. If your site uses Active Directory or a plain LDAP directory instead, the same package covers them; see the companion post.




