Flux CD
Hard
Integration
An ImageUpdateAutomation sets spec.policyChangeDelay: 2m, and ImagePolicy changes arrive at minutes 0, 1 and 3. What gets committed?
Select your answer:
Show answer and explanation
Answer: It commits the first two together at 2m and the third in a later run
Explanation
policyChangeDelay defers the run after an ImagePolicy change so that updates arriving within the delay land in one commit. The delay starts at the first change and later changes don't extend it, so the change at minute 3 misses that window and goes into a following run.
More hard Flux CD questions
- What does the annotation kustomize.toolkit.fluxcd.io/ssa: IfNotPresent do on an object in a Flux source?
- A change to an immutable field makes Flux's apply of a Job fail. Which annotation on the Job tells Flux to delete and recreate it?
- A GitRepository has no ref field, and the repository's default branch is main. What does Flux check out?
- kustomize-controller can't tell when a custom resource from a third-party operator is healthy. How do you teach it?
- You want to delete a Flux Kustomization but keep the workloads it created running. Which field do you set first?
- In a CI job, 'flux diff kustomization' exits with status 1. What does that mean?