Flux CD
Medium
Concepts
An ImagePolicy should pick the newest 1.x release tag and ignore 2.0 and later. Which policy fits?
Select your answer:
Show answer and explanation
Answer: policy.semver.range: '>=1.0.0 <2.0.0'
Explanation
A SemVer policy parses tags as versions and picks the highest one in the range, so 1.10.0 beats 1.9.0. Alphabetical ordering would rank 1.9.0 higher, and numerical policies need tags that are plain numbers, such as timestamps pulled out with filterTags.extract.
More medium Flux CD questions
- How can a push to Git make Flux fetch the new commit right away instead of waiting for the GitRepository interval?
- Which Flux setup reports deployment results back to GitHub as commit statuses?
- You delete a Flux Kustomization that has prune: true and no deletionPolicy. What happens to the objects it applied?
- Which file in a Git repository tells source-controller to leave files out of the artifact it builds?
- How can a HelmRelease install a chart that is stored in an OCI registry?
- A GitRepository sets both ref.branch: main and ref.tag: v1.2.0. Which one does Flux check out?