No GitOps reconciler — CI updates manifests but nothing applies them #3
Labels
No labels
auto-merge
blocked
claude
needs-review
upstream
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
espoautos/mdmz#3
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Problem
The CI pipeline (Forgejo Actions) builds images, pushes to registry, and commits updated
k8s/deployment.yamlwith the new image tag. However, there is no Flux, ArgoCD, or other GitOps operator running on the cluster to automatically apply these manifests.This means after CI completes, someone must manually
kubectl applythe updated deployment. This also means branding changes to deployment.yaml (like the ESPO | Chicago rename) don't take effect until manually applied.Options
kubectl applystep to CI — simplest, add a step after manifest commit that applies directly. Requires a kubeconfig/serviceaccount token in CI.Recommendation
Option 1 is the quickest. Add a final step to the CI workflow that uses
kubectl applywith a serviceaccount token. The op-api may already handle this — need to check.