k3s kubernetes 10846d1082 fix: root-cause Flux Setters silent no-op - namespace mismatch ... ImageUpdateAutomation only lists ImagePolicy objects in its own namespace (image-automation-controller's getPolicies() scopes the List() to obj.Namespace, confirmed by reading v1.2.4 source) - the $imagepolicy marker's namespace:name is only used to match against that pre-filtered list, not to broaden the search. Our ImageUpdateAutomation lived in flux-system while its ImagePolicy lived in hello-app, so the policy was invisible and Setters always found zero markers to update ("repository up-to-date" forever), regardless of correct marker syntax/RBAC/policy resolution. Moved ImageUpdateAutomation into the hello-app namespace (alongside its ImagePolicy), keeping a cross-namespace sourceRef back to the flux-system GitRepository. Also fixed the commit messageTemplate, which used the removed .Updated field (v1.2.4 requires .Changed). Verified live: Flux pushed commit 0273f15 updating deployment.yaml's tag on its own, and the cluster rolled out that image without any CI involvement. Removed the update-deployment-tag CI workaround job accordingly - it's redundant now and would otherwise race with Flux's own commits. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GJNvvV3RrvX6TRZGAKEUeY		2026-09-04 12:05:43 +01:00
..
build-hello-app.yml	fix: root-cause Flux Setters silent no-op - namespace mismatch	2026-09-04 12:05:43 +01:00
terraform.yml	Updated project to improve guidance	2026-09-03 19:06:27 +01:00