Shared memfile backend in kubernetes
We are trialling Kea in Kubernetes. We have scaled to multiple kea pods (currently two) for resilience and performance. For simplicity we're using a memfile backend to store leases that is shared between the pods. This is simultaneously writable by both pods (ReadWriteMany volume mode).
Can you advise any issues that may arise? In particular, I notice both pods are doing LFC cleanup. On a single kea, "if one [kea-lfc] is already running, the new process is terminated". But in our case, there's the possibility of two kea-lfcs running simultaneously. Will this break our memfile?
If so, this issue is a feature-request. We would prefer not to go to the effort of implementing a database-backend just for leases. The other benefits databases bring don't apply to us. We don't need per-host reservations\options, and would prefer to keep configuration in a simple file that we manage using git-ops. The ask would be: please add multi-server lease-file locking. This could be as simple as kea-lfc creating a temporary lock file for the duration of cleanup.