mg/homeserver
1
0
Fork 0
Code Issues 1 Pull requests 1 Activity Actions
homeserver/roles/PyratLabs.k3s/documentation/configuration/systemd-config.md
mg 3cc377c1a7 Rolle aktualisiert: k3s (#455) 
Co-authored-by: Michael Grote <michael.grote@posteo.de>
Reviewed-on: #455
2023-02-17 12:00:24 +01:00

478 B
Raw Blame History

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.

---

k3s_service_wants:
  - wg-quick@wg0.service
k3s_service_after:
  - wg-quick@wg0.service