roger/k3s-cluster
1
0
Fork 1
Code Issues Pull Requests 6 Actions Packages Projects Releases Wiki Activity

fix(myorg-assistant): fix CronJob images causing ImagePullBackOff #6

Closed
platform-engineer-agent wants to merge 1 commits from platform-engineer-agent/k3s-cluster:fix-cronjob-images into main
pull from: platform-engineer-agent/k3s-cluster:fix-cronjob-images
merge into: roger:main
Conversation 0 Commits 1 Files Changed 5 +20 -10
platform-engineer-agent commented 2026-07-06 02:59:15 +02:00
Collaborator
Copy Link

Problem

All 5 myorg-assistant CronJobs have been stuck in ImagePullBackOff for 9+ days because they reference myorg-assistant:latest — a bare image name with no registry prefix that doesn't exist anywhere.

Evidence (Prometheus):

myorg-deadline-checker-29721060-8kqmk: ImagePullBackOff
myorg-evening-summary-29719800-rn6rj: ImagePullBackOff
myorg-git-sync-29721075-kp4f4: ImagePullBackOff
myorg-morning-briefing-29720520-jktxn: ImagePullBackOff
myorg-waiting-followup-*: ImagePullBackOff

The main Deployment uses the correct image: git.rogi.casa/roger/myorg-assistant/myorg-assistant:fcf79bf (set in commit 3e57da4 on Jun 25), but the CronJobs were never updated.

Fix

For all 5 CronJobs:

  • Changed image to git.rogi.casa/roger/myorg-assistant/myorg-assistant:fcf79bf (same as Deployment)
  • Changed imagePullPolicy: IfNotPresent → Always (match Deployment)
  • Added imagePullSecrets: [{name: gitea-registry}] (required for private registry)

Once merged, ArgoCD selfHeal will pick up the change and the next CronJob runs will succeed.

## Problem All 5 myorg-assistant CronJobs have been stuck in `ImagePullBackOff` for 9+ days because they reference `myorg-assistant:latest` — a bare image name with no registry prefix that doesn't exist anywhere. Evidence (Prometheus): ``` myorg-deadline-checker-29721060-8kqmk: ImagePullBackOff myorg-evening-summary-29719800-rn6rj: ImagePullBackOff myorg-git-sync-29721075-kp4f4: ImagePullBackOff myorg-morning-briefing-29720520-jktxn: ImagePullBackOff myorg-waiting-followup-*: ImagePullBackOff ``` The main Deployment uses the correct image: `git.rogi.casa/roger/myorg-assistant/myorg-assistant:fcf79bf` (set in commit 3e57da4 on Jun 25), but the CronJobs were never updated. ## Fix For all 5 CronJobs: - Changed image to `git.rogi.casa/roger/myorg-assistant/myorg-assistant:fcf79bf` (same as Deployment) - Changed `imagePullPolicy: IfNotPresent` → `Always` (match Deployment) - Added `imagePullSecrets: [{name: gitea-registry}]` (required for private registry) Once merged, ArgoCD selfHeal will pick up the change and the next CronJob runs will succeed.
platform-engineer-agent added 1 commit 2026-07-06 02:59:17 +02:00
fix(myorg-assistant): fix cronjob images - use gitea registry + imagePullSecrets 48f84dceb1 
CronJobs referenced bare 'myorg-assistant:latest' which doesn't exist in
any registry, causing ImagePullBackOff on all 5 CronJobs for 9+ days.
Aligned with deployment.yaml:
  - image: git.rogi.casa/roger/myorg-assistant/myorg-assistant:fcf79bf
  - imagePullPolicy: Always
  - imagePullSecrets: gitea-registry

Affected: deadline-checker, evening-summary, git-sync, morning-briefing, waiting-followup

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
platform-engineer-agent roger
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: roger/k3s-cluster#6
No description provided.
Delete Branch "platform-engineer-agent/k3s-cluster:fix-cronjob-images"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?