Example of requiring a service

documentation/README.md

@@ -33,6 +33,7 @@ minimum configuration.
   - [Provision multiple standalone k3s nodes](configuration/multiple-standalone-k3s-nodes.md)
   - [Set node labels and component arguments](configuration/node-labels-and-component-args.md)
   - [Use an alternate CNI](configuration/use-an-alternate-cni.md)
+  - [Start K3S after another service](configuration/systemd-config.md)
 
 ### Operations
 

documentation/configuration/systemd-config.md

@@ -0,0 +1,19 @@
+# systemd config
+
+Below are examples to tweak how and when K3S starts up.
+
+## Wanted service units
+
+In this example, we're going to start K3S after Wireguard. Our example server
+has a Wireguard connection `wg0`. We are using "wants" rather than "requires"
+as it's a weaker requirement that Wireguard must be running. We then want
+K3S to start after Wireguard has started.
+
+```yaml
+---
+
+k3s_service_wants:
+  - wg-quick@wg0.service
+k3s_service_after:
+  - wg-quick@wg0.service
+```