Flux CD
Hard
Testing
In a CI job, 'flux diff kustomization' exits with status 1. What does that mean?
Select your answer:
Show answer and explanation
Answer: It found differences between the local manifests and the cluster
Explanation
flux diff exits with 0 when there are no differences, 1 when it finds some, and above 1 when the diff itself fails. A CI step that fails on any non-zero exit will fail on every pull request that changes something, so treat only codes above 1 as errors.
More hard Flux CD questions
- A chart ships CRDs in its crds/ directory, and the HelmRelease has no crds settings. What happens to those CRDs on upgrade?
- How many Helm release revisions does helm-controller keep for a HelmRelease that doesn't set maxHistory?
- A HelmRelease sets upgrade.remediation.retries: 3 and nothing else under remediation. What happens between failed upgrade attempts?
- How does notification-controller build the webhook URL path for a Receiver?
- A HelmRelease's chartRef points at an OCIRepository holding a Helm chart. How should the OCIRepository's layerSelector handle the chart layer?
- How can you make Flux refuse an OCI artifact that wasn't signed by your CI pipeline?