feat: remove KV for config/dynamic config generation #761

New issue

Closed

opened 2026-03-28 04:28:16 +00:00 by mfreeman451 · 0 comments

mfreeman451 commented

2026-03-28 04:28:16 +00:00

Owner

Imported from GitHub.

Original GitHub issue: #2332
Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/issues/2332
Original created: 2026-01-18T05:40:15Z

Is your feature request related to a problem?

We are going to remove the ability to talk to/get config from the KV, on the edge collectors. There is really no need to be able to generate dynamic config for these services, nothing ever will change, and it just means we have to build more complicated config compilers in the core.

Eligible for cleanup:

flowgger
trapd
new inbound netflow PR
zen?
otel

We should be able to make a clean break in pkg/config and completely remove all of the KV config code here and cleanup the affected services (rust and golang), we might also be able to get rid of rust/kvutil dont know if we need that anymore, and all of these services can just use json/yaml instead, and some of them will get their config over GRPC (serviceradar-agent). The elixir based services are all out of scope for this and none of them have been built around the KV config stuff anyways.

Describe the solution you'd like

A clear and concise description of what you want to happen.

Describe alternatives you've considered

A clear and concise description of any alternative solutions or features you've considered.

Additional context

Add any other context or screenshots about the feature request here.

Imported from GitHub. Original GitHub issue: #2332 Original author: @mfreeman451 Original URL: https://github.com/carverauto/serviceradar/issues/2332 Original created: 2026-01-18T05:40:15Z --- **Is your feature request related to a problem?** We are going to remove the ability to talk to/get config from the KV, on the edge collectors. There is really no need to be able to generate dynamic config for these services, nothing ever will change, and it just means we have to build more complicated config compilers in the core. Eligible for cleanup: - [ ] flowgger - [ ] trapd - [ ] new inbound netflow PR - [ ] zen? - [ ] otel We should be able to make a clean break in `pkg/config` and completely remove all of the KV config code here and cleanup the affected services (rust and golang), we might also be able to get rid of `rust/kvutil` dont know if we need that anymore, and all of these services can just use json/yaml instead, and some of them will get their config over GRPC (serviceradar-agent). The elixir based services are all out of scope for this and none of them have been built around the KV config stuff anyways. **Describe the solution you'd like** A clear and concise description of what you want to happen. **Describe alternatives you've considered** A clear and concise description of any alternative solutions or features you've considered. **Additional context** Add any other context or screenshots about the feature request here.