3 ms·
My understanding was that K8s itself has overhead, which ultimately has to be paid for, even if using a managed service (it might be included in the cost of wha
by shrubble 3y ago
My understanding was that K8s itself has overhead, which ultimately has to be paid for, even if using a managed service (it might be included in the cost of what you pay, of course).
I did add the caveat of "with modules" and the idea of sharing values around to different servers would be easy to do, since you have Postgres around as a database to hold those values/statuses.
- paulgb 3y agoHTTP proxying is not much of our codebase. I wouldn’t want to shoehorn what we’re doing into being a module of a proxy service just to avoid writing that part. That proxy doesn’t run on Kubernetes currently anyway, so it wouldn’t change anything we currently use Kubernetes for.