safeguarding k3s & removing fwmgr from machines that have hardware with no upstream updates
This commit is contained in:
1 parent
4c8efd185d
commit
39f062a7af
10 files changed
+5
-30
No files matched your search
@@ -216,6 +216,8 @@ in
|
||||
wantedBy = [ "multi-user.target" ];
|
||||
serviceConfig = {
|
||||
Type = "oneshot";
|
||||
Restart = "on-failure";
|
||||
RestartSec = "15s";
|
||||
RemainAfterExit = true;
|
||||
Environment = "KUBECONFIG=/etc/rancher/k3s/k3s.yaml";
|
||||
ExecStart = "${pkgs.kubectl}/bin/kubectl apply -f ${agentManifest}";
|
||||
@@ -230,6 +232,8 @@ in
|
||||
wantedBy = [ "portainer-agent-k3s.service" ];
|
||||
serviceConfig = {
|
||||
Type = "oneshot";
|
||||
Restart = "on-failure";
|
||||
RestartSec = "15s";
|
||||
RemainAfterExit = true;
|
||||
Environment = "KUBECONFIG=/etc/rancher/k3s/k3s.yaml";
|
||||
};
|
||||
|
||||
Reference in new issue
Block a user