search

techno-tim / k3s-ansible

The easiest way to bootstrap a self-hosted High Availability Kubernetes cluster. A fully automated HA k3s etcd install with kube-vip, MetalLB, and more. Build. Destroy. Repeat.
https://technotim.live/posts/k3s-etcd-ansible/
Apache License 2.0
2.41k stars 1.05k forks source link

Change snapshotter to native driver if LXC is using zfs backend #232

Closed Nomsplease closed 1 year ago

Nomsplease commented 1 year ago

Proposed Changes

Fixes https://github.com/techno-tim/k3s-ansible/issues/230

If using LXC containers on Proxmox with a ZFS pool, the overlay driver will cause k3s to not start which will cause failure to deploy. This corrects that behavior by checking for /var/lib to be backed by zfs and changes the snapshot driver to native.

This is part of the lxc role, so this will not affect any bare metal deployments. This is intentional as I did not validate bare metal deployments.

Checklist

Nomsplease commented 1 year ago

Dont merge this. I cant be sure if this is a edge case or not in my scenario now. If we have examples that this is more then an edge case then we have a fix, otherwise it will be relegated to the history of PRs.