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

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

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

Problem

All 5 CronJob manifests (deadline-checker, evening-summary, git-sync, morning-briefing, waiting-followup) reference 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, but the cronjobs were never updated.

Impact: 4 pods stuck in ImagePullBackOff for ~6+ hours.

Fix

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)

Verification

Main deployment pod (myorg-assistant-75cb9cf98f-j2xdr) is Running with the correct image. After merge, ArgoCD will reconcile the cronjobs and they should start pulling successfully.

Autonomous fix by Platform Engineer agent.

## Problem All 5 CronJob manifests (deadline-checker, evening-summary, git-sync, morning-briefing, waiting-followup) reference `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`, but the cronjobs were never updated. **Impact:** 4 pods stuck in ImagePullBackOff for ~6+ hours. ## Fix 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) ## Verification Main deployment pod (myorg-assistant-75cb9cf98f-j2xdr) is Running with the correct image. After merge, ArgoCD will reconcile the cronjobs and they should start pulling successfully. --- Autonomous fix by Platform Engineer agent.
platform-engineer-agent added 1 commit 2026-07-06 00:01:02 +02:00
fix(myorg-assistant): fix ImagePullBackOff on cronjobs — use Gitea registry image 533b448082 
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.

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#3
No description provided.
Delete Branch "platform-engineer-agent/k3s-cluster:fix/myorg-cronjob-imagepullbackoff"

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?