OCI source by semver
Track an OCI artifact by semver range instead of git; modern: GitOps from a registry
flux create source oci <name> --url=oci://reg/repo --tag-semver='>=1.0.0' --interval=5m
- tool
- flux29 commands
More flux commands
-
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
-
flux diff kustomization <name> --path ./overlays/prodServer-side dry-run showing exactly what Flux would change before applying
-
flux tree kustomization <name>List every object a kustomization owns, including nested kustomizations
-
flux build kustomization <name> --path ./ | kubectl apply --dry-run=server -f -Render the final manifests offline with Flux substitutions, then validate server-side
-
flux get images all -AShow all ImageRepositories, policies and update automations across namespaces