You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 14, 2020. It is now read-only.
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.
Is there recomended way of extending configuraiton ?
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
The text was updated successfully, but these errors were encountered:
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:
ConfigMap
into operatorDeployment
and read the file fromConfigMap
insideon.startup
handlerBut all of those are requiring some custom development and boilerplate code for every new operator created with
kopf
.Checklist
Keywords
config, configuration
The text was updated successfully, but these errors were encountered: