Is your feature request related to a problem ?
We are seeing disk IO exhaustion as Kustomize uses the temp volume.
One recommendation, which we have done successfully using manual patching, is to mount the temp folder as in-memory.
However, as it stands that isn't possible with the helm chart, as it always writes out the first temp mount, no matter what values are supplied.
Can we change the chart so that this temp mount can be disabled?
It is force set here:
And similarly in the other controllers.
We would like to provide config like this:
kustomizeController:
volumes:
- name: temp
emptyDir:
sizeLimit: 1000Mi
medium: Memory
volumeMounts:
- name: temp
mountPath: /tmp
but we see errors that mappings for "/tmp" are duplicated.
Describe the solution you'd like.
Have config that allows disabling writing out the standard temp folder. Or maybe a "smart all in one config" that is "use in-memory config for temp folder".
Describe alternatives you've considered.
Working from a fork of the helm chart, but that is not long term.
Additional context.
Discussed here: fluxcd/flux2#3380 (reply in thread)
Is your feature request related to a problem ?
We are seeing disk IO exhaustion as Kustomize uses the temp volume.
One recommendation, which we have done successfully using manual patching, is to mount the temp folder as in-memory.
However, as it stands that isn't possible with the helm chart, as it always writes out the first temp mount, no matter what
valuesare supplied.Can we change the chart so that this temp mount can be disabled?
It is force set here:
helm-charts/charts/flux2/templates/kustomize-controller.yaml
Line 112 in e07cfac
And similarly in the other controllers.
We would like to provide config like this:
but we see errors that mappings for "/tmp" are duplicated.
Describe the solution you'd like.
Have config that allows disabling writing out the standard temp folder. Or maybe a "smart all in one config" that is "use in-memory config for temp folder".
Describe alternatives you've considered.
Working from a fork of the helm chart, but that is not long term.
Additional context.
Discussed here: fluxcd/flux2#3380 (reply in thread)