Ask HN: Do you use k8s ConfigMap for “business” logic application configuration?

1 point·tomerbd··3 comments

Is using k8s configMap for business logic application config considered a good use case? Non best practice? Do you prefer storing you application configuration somewhere else? Why?

View on HN

KISS: Use env vars for container configuration if at all possible

I might be oversimplifying but ConfigMap is essentially a workaround to adapt file system based configuration to the docker env var pattern. Use it if you have to

There may be some CKADs who have a more informed opinion than me on this.

Why not store the configuration in a dedicated configuration service and let the app fetch them from this configuration server without the need to go through the environment variables layer? Wouldn't it simplify a use case where you have both web and mobile app and have them both fetch configuration in the same way?

One comes with all processes & is standard. What standards if any would we use if any for holding config in services? gRPC with config defined in app-specific/bespoke protobuf schemas? Custom OpenAPI per app?

I ask myself what is thr known quantity that will have the nest tools & support & third flexibility. Given how vast the support base for env vars, how well known they are, and how miscellanious & varied & small-fry & specific most alternatives would be, it feels like a lock.

The only thing I can think if as better & more scriptable is directories of small files. 9p esque filesystems. Cause wow are we good at managing filesystems. But we're at risk of having too many ways to use them & too many tools to have a clear & shared forward path.

Reply on news.ycombinator.com