Platform Engineer 533b448082 fix(myorg-assistant): fix ImagePullBackOff on cronjobs — use Gitea registry image ...

All 5 CronJob manifests (deadline-checker, evening-summary, git-sync,
morning-briefing, waiting-followup) referenced 'myorg-assistant:latest'
—a bare local image name that doesn't exist on any node. The main
Deployment already uses git.rogi.casa/roger/myorg-assistant/myorg-assistant:fcf79bf.

Changes per cronjob:
- image: myorg-assistant:latest → git.rogi.casa/.../myorg-assistant:fcf79bf
- imagePullPolicy: IfNotPresent → Always (match Deployment)
- Add imagePullSecrets: gitea-registry (required for private registry)

This fixes 4 pods stuck in ImagePullBackOff for ~6+ hours.

2026-07-05 22:00:36 +00:00

..

deadline-checker.yaml

fix(myorg-assistant): fix ImagePullBackOff on cronjobs — use Gitea registry image

2026-07-05 22:00:36 +00:00

evening-summary.yaml

fix(myorg-assistant): fix ImagePullBackOff on cronjobs — use Gitea registry image

2026-07-05 22:00:36 +00:00

git-sync.yaml

fix(myorg-assistant): fix ImagePullBackOff on cronjobs — use Gitea registry image

2026-07-05 22:00:36 +00:00

morning-briefing.yaml

fix(myorg-assistant): fix ImagePullBackOff on cronjobs — use Gitea registry image

2026-07-05 22:00:36 +00:00

waiting-followup.yaml

fix(myorg-assistant): fix ImagePullBackOff on cronjobs — use Gitea registry image

2026-07-05 22:00:36 +00:00