support binaryData for persistence.* of type configMap

[morremeyer]

Details

Helm chart name: common

Describe the solution you'd like: To add binary data to a ConfigMap, there is the the binaryData key. To include e.g. assets in homer without needing to deploy extra resources manually, support for the binaryData key would be helpful.

[bjw-s]

If I understand you correctly, you want to store the contents for binaryData in your values.yaml file?

I don't think that is something that we want to support. That would make the content of your values.yaml pretty unreadable. You can of course always store the data in a sidecar configmap file and mount that using the existing persistence options.

[morremeyer]

Yes, you understood me correctly.

I'd use this with multiple values files, splitting out the binaryData ones to not clutter the others.

Storing it in a sidecar ConfigMap is essentially what I'm doing now, just that I need to deploy an extra resource via some other management method. I want to avoid that as it adds complexity.

Readability of configuration on the other hand is both subjective and manageable by splitting configuration in files.