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

fix(myorg-assistant): add WEB_SECRET_KEY env to cronjobs #19

Closed
platform-engineer-agent wants to merge 3 commits from platform-engineer-agent/k3s-cluster:main into main
pull from: platform-engineer-agent/k3s-cluster:main
merge into: roger:main
Conversation 0 Commits 3 Files Changed 6 +51 -10
platform-engineer-agent commented 2026-07-12 01:52:44 +02:00
Collaborator
Copy Link

Stops pydantic Settings validation crash loop in all 5 myorg cronjobs (only Deployment had WEB_SECRET_KEY). git-sync trips >3 restarts/15m. Match Deployment by adding secret-sourced WEB_SECRET_KEY env.

Stops pydantic Settings validation crash loop in all 5 myorg cronjobs (only Deployment had WEB_SECRET_KEY). git-sync trips >3 restarts/15m. Match Deployment by adding secret-sourced WEB_SECRET_KEY env.
platform-engineer-agent added 3 commits 2026-07-12 01:52:46 +02:00
fix(argocd): add ignoreDifferences to root app to stop Application CRD drift loop 962ffd5200 
The k3s-cluster-root app-of-apps has been in a continuous Synced<->OutOfSync
oscillation (489 transitions in 24h). Each cycle, ArgoCD syncs the 'argocd'
Application CRD, succeeds, then immediately detects drift because ArgoCD
adds status/operation fields to Application resources at runtime.

Adding ignoreDifferences for /status and /operation on Application resources
stops the drift loop while keeping the app-of-apps functional.
fix(myorg-assistant): point cronjobs at registry image + add imagePullSecrets aab38aa67b 
CronJob pods were stuck in ImagePullBackOff because they referenced
the local-only image 'myorg-assistant:latest' which is not present
on the node. Switch all 5 cronjobs to the Gitea registry image
git.rogi.casa/roger/myorg-assistant/myorg-assistant:fcf79bf
(matching the Deployment), set imagePullPolicy: Always, and add
imagePullSecrets: gitea-registry so they can authenticate to the
private registry.
fix(myorg-assistant): add WEB_SECRET_KEY env to cronjobs to stop pydantic Settings validation crash 70ad508180

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#19
No description provided.
Delete Branch "platform-engineer-agent/k3s-cluster:main"

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?