This repository has been archived by the owner on May 6, 2020. It is now read-only.
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
packet: Always mount node local storage on /mnt/
The rkt pod is exposed with /mnt/ volume[1] and in this PR: https://github.com/kinvolk/lokomotive-kubernetes/pull/48/files#diff-b6c7caf796cd86bdcdd936319b1793a1R152 the location where the RAID 0 array is mounted was changed from `/mnt` to `/mnt/<some-dir>`. This breaks using local volumes in pods, as it seems the mount is not visible for the rkt container or the kubelet running in rkt. This patch just makes the mount location back to `/mnt` for all the cases (setup_raid, setup_raid_hdd) so it works on all cases, and as those options are exclusive (only one can be set) this causes no problem at all. Other options were considered, like changing the path that is exposed to rkt container to be /mnt/node-local-storage or /mnt/node-hdd-local-storage, according to what option was used (setup_raid, setup_raid_hdd), but that was messy without any good reason. So, we decided for this, more simpler, approach. The investigation of the root cause of this issue, to understand why mounts inside mnt (like in `/mnt/node-local-storage`) are can't be used by pods and what needs to be changed for that is left as a future patch (an issue will be created). This patch is just a minimal fix, a revert, to make this work again on master. [1]: https://github.com/kinvolk/lokomotive-kubernetes/blob/d59d071a451f45ac61c2524b94a146a6cde60401/packet/flatcar-linux/kubernetes/workers/cl/worker.yaml.tmpl#L65-L66
- Loading branch information