local path provisioner issues
There are several issues with the local path provisioner
-
Why are we even using a custom image?
- Well, I did some research, and the reason why is that we use a
Volume
instead of ahostPath
. Using a volume allows us to use Velero for backups, which (at least at the time we were figuring this out) does not support backing up hostPaths. I couldn't find the issue and/or a PR from us where we discussed this (@arie do you remember?), but I did find our code: https://github.com/greenhost/local-path-provisioner
- Well, I did some research, and the reason why is that we use a
-
The image we currently use does not exist anymore.
-
For now I'll re-build our fork and push it again, so our CI pipeline works again.
-
-
Our CI pipeline does not confirm that the
local-path-provisioner
helmrelease succeeds.-
We'll need to add that too
-
-
Update and properly tag our fork #946 (closed) | !490 (merged) -
Make / find a PR to push using volumes instead of hostPath upstream (https://github.com/rancher/local-path-provisioner/issues/85, points to https://github.com/rancher/rancher/issues/22061 which is a rancher issue and we're not going to make a PR for rancher) -
Document why we use a certain, old revision of the official rancher local-path-provisioner git repo in flux2/infrastructure/sources/local-path-provisioner.yaml
(also done in !490 (merged))