K3s: Difference between revisions
imported>Mic92 add multi-node setup |
imported>Vater m specific kind of software |
||
| Line 21: | Line 21: | ||
See this [https://github.com/Mic92/doctor-cluster-config/tree/master/modules/k3s real world example]. You might want to ignore some parts of it i.e. the monitoring as this is specific to our setup. | See this [https://github.com/Mic92/doctor-cluster-config/tree/master/modules/k3s real world example]. You might want to ignore some parts of it i.e. the monitoring as this is specific to our setup. | ||
The | The K3s server needs to import <code>modules/k3s/server.nix</code> and an agent <code>modules/k3s/agent.nix</code>. | ||
Tipp: You might run into issues with coredns not being reachable from agent nodes. Right now we disable the NixOS firewall all together until we find a better solution. | Tipp: You might run into issues with coredns not being reachable from agent nodes. Right now we disable the NixOS firewall all together until we find a better solution. | ||
== ZFS support == | == ZFS support == | ||
K3s's builtin containerd does not support the zfs snapshotter. However it is possible to configure it to use an external containerd: | |||
<syntaxHighlight lang=nix> | <syntaxHighlight lang=nix> | ||
| Line 38: | Line 38: | ||
[[Category:Applications]] | [[Category:Applications]] | ||
[[Category:Server]] | [[Category:Server]] | ||
[[Category:orchestration]] | |||