Question

Your team uses Flux for GitOps delivery. A separate CI pipeline builds and pushes a new container image tag to the registry each time code merges to main. You want new image tags to be deployed automatically without a developer manually editing the manifest in Git. Which Flux capability accomplishes this while keeping Git as the source of truth?

Accepted Answer

Flux image automation, which scans the registry for new tags and writes the updated image reference back to the Git repository as a commit

Answer

Configuring Flux to pull the ':latest' tag so every reconciliation always deploys the newest image directly from the registry

Answer

Adding a CI step that runs 'kubectl set image' against the cluster immediately after the image is pushed

Answer

Enabling Flux drift detection so it treats the newer registry image as the desired state and self-heals toward it