Flux CD
Hard
Architecture
How many Helm release revisions does helm-controller keep for a HelmRelease that doesn't set maxHistory?
Select your answer:
Show answer and explanation
Answer: 5
Explanation
helm-controller keeps 5 revisions by default, half of the Helm CLI's default of 10. Older revision Secrets are removed after each upgrade. Setting maxHistory: 0 keeps every revision, which the Flux docs advise against for performance reasons.
More hard Flux CD questions
- 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?
- Which GitRepository setting makes Flux check that the tag it checks out was signed with a trusted PGP key?
- One kustomize-controller can't keep up with thousands of Kustomizations. How does Flux split the work?