Reapplying generated flux manifests will erase known_host customisation

[Michael Bridgen]

For some uses of Flux (or weave-flux-agent) it is necessary to customise the deployment manifest; for example, if you're using a self-hosted git server, you need to mount a known_hosts file (see fluxcd/flux#724) from a configmap volume. Unfortunately, as soon as the launcher reapplies the generated manifest, the volume and mount will disappear.

In this case, putting the known_hosts (and .ssh/config?) in a configmap and always mounting it might work. We would have to only supply the initial configmap when the person is installing flux.

[Jesus Vazquez]

👋 I'm having this issue. I had to overwrite the deployment of weave-flux-agent to include the ssh config volume and disable weave-agent with replicas set to 0 to avoid overrides.

Thats the only workaround that I know.