Configure Kubeless with mounted config files not by directly accessing a ConfigMap resource

[andrascz]

Is this a BUG REPORT or FEATURE REQUEST?: feature request

What happened: it is a cumbersome burden that ConfigMap allows only a string->string mapping to be defined.

What you expected to happen: It would be better to be able to map files into a configmap. This could be enabled by #1202 and using a ConfigMap resource templated with something like {{ (.Files.Glob "config/*").AsConfig | indent 2 }}
See, the Helm docs for further details.

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:
Together with #1201 this could eliminate any need to directly use the Kuberentes API, except for accessing the Function resources themselves. See #1197 for the benefits of this.
See https://github.com/envoyproxy/ratelimit/#loading-configuration for a possible solution for hot reloading the configuration.

Environment:

• Kubernetes version (use kubectl version):
• Kubeless version (use kubeless version):
• Cloud provider or physical cluster: