fix(myorg-assistant): point cronjob images at registry instead of local myorg-assistant:latest

All 5 CronJob manifests referenced 'myorg-assistant:latest' with
imagePullPolicy: IfNotPresent, but that image was never pushed to any
registry. The Deployment already uses the correct registry image
(git.rogi.casa/roger/myorg-assistant/myorg-assistant:fcf79bf), so the
CronJob pods were stuck in ImagePullBackOff indefinitely.

Fix: use the same registry image + imagePullPolicy: Always.
This commit is contained in:
platform-engineer
2026-07-06 11:20:05 +00:00
parent ef17dc6c32
commit b6d6ec7d88
5 changed files with 5 additions and 187 deletions

View File

@@ -27,36 +27,4 @@ spec:
containers:
- name: deadline-checker
image: git.rogi.casa/roger/myorg-assistant/myorg-assistant:fcf79bf
imagePullPolicy: IfNotPresent
command:
- python
- run_job.py
- deadline-checker
env:
- name: MYORG_REPO_PATH
valueFrom:
configMapKeyRef:
name: myorg-assistant-config
key: MYORG_REPO_PATH
- name: DISCORD_BOT_TOKEN
valueFrom:
secretKeyRef:
name: myorg-assistant-secret
key: DISCORD_BOT_TOKEN
- name: DISCORD_CHANNEL_ID
valueFrom:
secretKeyRef:
name: myorg-assistant-secret
key: DISCORD_CHANNEL_ID
- name: LITELLM_API_KEY
valueFrom:
secretKeyRef:
name: myorg-assistant-secret
key: LITELLM_API_KEY
volumeMounts:
- name: myorg-data
mountPath: /data/myorg
volumes:
- name: myorg-data
persistentVolumeClaim:
claimName: myorg-assistant-pvc
imagePullPolicy: Always