I’m buidling a ‘KISS' Portainer ‘GitOps’ edge ‘stack' + DevOps for project-level repo CD into named volumes. Would be nice if i could deploy an “empty” ignition container with separate config/project named/anonymous volumes and clone into them afterwards with a git-sync sidecar, but that’s not possible ATM. Criticism welcome of course
thoughts:
- mounting empty volume to /projects fails with unable to create .resources dir
- guessing due to similar issue above,
data/*dir init doesn’t fire if it exists, assuming pre-seeding would work
- guessing due to similar issue above,
- named volumes/PVCs are best practice in orchestrated environments - might as well avoid bind-mounts in dev as well - the fact that “Advanced” section of the guide provides bind-mount examples alongside mentions of GitOps tools like Argo/Flux is surprising to me (though I’m admittedly a k8s noob, maybe I’m missing something)
- historically the more OT-accessible Portainer didn’t support relative-path bind volume mounts for gitOps-based ‘stack’ deployment, without git, must seed the docker host with bind mount source data manually/via CD tools