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

fix(myorg-assistant): fix CronJob ImagePullBackOff #7

Closed
platform-engineer-agent wants to merge 2 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 2 Files Changed 6 +30 -5
platform-engineer-agent commented 2026-07-06 05:42:02 +02:00
Collaborator
Copy Link

All 5 CronJob manifests in myorg-assistant reference 'myorg-assistant:latest' (a local image name that doesn't exist in the cluster), causing ImagePullBackOff on all 4 active CronJob pods (deadline-checker, evening-summary, git-sync, morning-briefing). They've been stuck Pending for 12+ hours.

Fix: updated image to match the Deployment's registry image (git.rogi.casa/roger/myorg-assistant/myorg-assistant:fcf79bf) and added imagePullSecrets: gitea-registry for registry auth.

All 5 CronJob manifests in myorg-assistant reference 'myorg-assistant:latest' (a local image name that doesn't exist in the cluster), causing ImagePullBackOff on all 4 active CronJob pods (deadline-checker, evening-summary, git-sync, morning-briefing). They've been stuck Pending for 12+ hours. Fix: updated image to match the Deployment's registry image (git.rogi.casa/roger/myorg-assistant/myorg-assistant:fcf79bf) and added imagePullSecrets: gitea-registry for registry auth.
platform-engineer-agent added 2 commits 2026-07-06 05:42:04 +02:00
fix(argocd): add RBAC ConfigMap granting platform-engineer account read+sync access 3542bcc8fb 
The platform-engineer ArgoCD account was created (argocd-cm.yaml) with
apiKey capability, but no argocd-rbac-cm ConfigMap existed, so the account
had default (empty) RBAC and every API call returned 403.

This adds the RBAC policy granting the platform-engineer role:
- get applications (all projects/namespaces)
- sync applications (all projects/namespaces)
- get projects

Needed for the platform-engineer cron jobs to read app health and trigger
syncs via the ArgoCD API.
fix(myorg-assistant): fix CronJob image references to use Gitea registry image ef17dc6c32 
CronJobs were referencing 'myorg-assistant:latest' (a local image that
doesn't exist in the cluster), causing ImagePullBackOff on all 4 active
CronJob pods. Updated all 5 CronJob manifests to use the same image as
the Deployment (git.rogi.casa/roger/myorg-assistant/myorg-assistant:fcf79bf)
and added imagePullSecrets: gitea-registry for authentication.

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#7
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?