Config Management Enhancements

[kralicky]

We need to design a system to consolidate all the gateway, agent, and plugin config files (and maybe configuration for other opni components) in a single place. I want to start a discussion and gather requirements from different teams so we can plan a design for an enhanced config system.

Features needed for monitoring:

• Hot-reload with callbacks
• A clean way to get config objects into plugins, preferably without fetching them directly through the management api
• An API for updating config fields for the UI/CLI to use

Unknowns:

• Where to store config files?
• How to structure configs?
• How should hot-reloading work?
• Should we define the config with protobuf?
• Are there any libraries we can use?
• How does the KV store fit into this?

[dbason]

It might be worth checking into how Rancher stores its configuration currently. I would tend to storing it in a k8s object, but not sure if this would best be a json blob stored in a ConfigMap or a custom resource.

[sanjay920]

https://ranchermanager.docs.rancher.com/getting-started/overview#features-of-the-rancher-api-server

[dbason]

Yeah I meant more from a code point of view. More specifically how it stores these settings:

[alexandreLamarre]

I'd be in favour of looking for a library that programmatically creates config file(s) with developer friendly methods, independent of the physical formats its translated to. I was using something similar in rust a while back.

Not sure if such a go library exists, we tend to be very reliant in go on json, yaml , kubebuilder, etc... tags for something like that

[kralicky]

Which Rust library is that?