Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Revert "Create xtables.lock as a file if it doesn't already exist"
This reverts commit 93f8d3a. The xtables.lock mount was fixed to specify its type: it must exist as a file, or be created as a file. xtables.lock is only used with legacy iptables. On platforms using iptables-nft, the file isn't used and doesn't exist. As a result, previous versions of Submariner created it as a directory (this is the default behaviour for volume mounts in Kubernetes: if the mount doesn't exist, it is created as a directory). When the volume mount type is specified as a file, the existence of a directory causes the mount to fail and the corresponding pod is never scheduled. To avoid this, revert to the default behaviour. On systems where the lock is important, it already exists so the directory isn't created and the correct behaviour is guaranteed. On systems where the lock isn't needed, it is created as a directory but that doesn't matter. Future releases of Submariner will have to deal with this correctly, and handle upgrades, ideally without mounting all of /run permanently. Signed-off-by: Stephen Kitt <[email protected]>
- Loading branch information