[question] How to provide custom configuration for an operator ?

[kopf-archiver]

An issue by eshepelyuk at 2020-05-14 09:48:57+00:00
Original URL: zalando-incubator/kopf#367
 

Question

Somehow related to discussion from #280

I wan't to pass some configuration to an operator with quite complex nested structure, eg. JSON, YAML etc. Currently I haven't found any standard way of providing and injecting such config into operator handler.

The possible options I could use to achieve my goal is:

• pass values as ENV vars, but this is not applicable for complex data structures
• inject ConfigMap into operator Deployment and read the file from ConfigMap inside on.startup handler
• embed kopf and pass through parameters to kopf, retrieving from from CLI

But all of those are requiring some custom development and boilerplate code for every new operator created with kopf.

1. Is there recomended way of extending configuraiton ?
2. Is there plan to provide some generic component for such uses cases ?

Checklist

• I have read the documentation and searched there for the problem
• I have searched in the GitHub Issues for similar questions

Keywords

config, configuration

[nolar]

Pre-released in kopf>=1.30.0rc1, docs: https://kopf.readthedocs.io/en/latest/memos/

Includes cross-handler data exchange (incl. cross-resource-&-operator-handlers) and arbitrary structs for embedded operators.

FYI, @eshepelyuk.