Flux CD
Hard
Architecture
A HelmRelease's chartRef points at an OCIRepository holding a Helm chart. How should the OCIRepository's layerSelector handle the chart layer?
Select your answer:
Show answer and explanation
Answer: Select the Helm chart media type with operation: copy
Explanation
layerSelector picks a layer by media type, here application/vnd.cncf.helm.chart.content.v1.tar+gzip. The default operation, extract, unpacks the layer; copy keeps the chart tarball unchanged, which is how the HelmRelease docs configure it. Without a layerSelector, the first layer is extracted.
More hard Flux CD questions
- 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?
- What does 'flux reconcile kustomization my-app' change on the object to trigger a reconciliation?
- A ConfigMap applied by a Flux Kustomization holds a shell script using ${HOME}, and postBuild substitution blanks it out. What stops that?
- A HelmRelease in flux-system sets targetNamespace: apps and no storageNamespace. Where does Helm keep the release's storage Secrets?