Push image policy

Define which image tags Flux should track for automation

flux create image policy <name> --image-ref=<image-repo> --select-semver='>=1.0.0' -n flux-system
tool
flux29 commands
tags
flux

More flux commands

  • OCI source by semver
    flux create source oci <name> --url=oci://reg/repo --tag-semver='>=1.0.0' --interval=5m

    Track an OCI artifact by semver range instead of git; modern: GitOps from a registry

  • Push manifests as OCI artifact
    flux push artifact oci://reg/manifests:$(git rev-parse --short HEAD) --path=./manifests --source=$(git config --get remote.origin.url) --revision=$(git rev-parse HEAD)

    Package manifests into an OCI artifact tagged by commit; note: embeds source+revision metadata

  • Diff kustomization vs cluster
    flux diff kustomization <name> --path ./overlays/prod

    Server-side dry-run showing exactly what Flux would change before applying

  • Tree of managed objects
    flux tree kustomization <name>

    List every object a kustomization owns, including nested kustomizations

  • Build kustomization locally
    flux build kustomization <name> --path ./ | kubectl apply --dry-run=server -f -

    Render the final manifests offline with Flux substitutions, then validate server-side

all 29 flux commands