forked from roger/k3s-cluster
ba7e05a73d
The git-sync CronJob only ran `git pull`/`git push` against /data/myorg but never ensured the repo existed. The clone was solely the Deployment's git-clone initContainer's job, and when that didn't populate the volume the cron pod failed with 'Not a git repository: /data/myorg' on every run (and swallowed the error, exiting 0). Add an idempotent git-clone initContainer (guarded by [ ! -d /data/myorg/.git ]) so the cron job self-heals and actually syncs. Refs: myorg-git-sync-* 'Pull: Error: Not a git repository' (last 24h+)