Include known_hosts in secret to make it a bit easier to mount into container

[squaremo]

Either as the standard way of deploying it, or as an alternative means of overriding known_hosts (as in #724).

[squaremo]

Alternative: put known_hosts and config in a configmap that is always mounted. That way people can override them, while reapplying the standard configuration without losing their overrid-- .. their overris-- ... their customisation.

[squaremo]

Maybe a docker-config too? (e.g., as generated from sidecars, like the workaround posted in #539)

NB one thing to keep in mind: if you mount a secret or configmap using subPath, the files won't get updated when the resources do.

[hiddeco]

NB one thing to keep in mind: if you mount a secret or configmap using subPath, the files won't get updated when the resources do.

You can get around this by specifying .configMap.items in combination with a mountPath as mounted ConfigMaps are updated automatically.

The downside of this approach is that it overwrites all the original data in the mountPath (if any).

You can however get around this (again) by creating a symlink to your mountPath (e.g. /home/flux/.ssh/known_hosts -> /home/flux/config/known_hosts).

[supra08]

@2opremio I would like to work on this issue.