4 ms·
I've worked on a lot of very large Kubernetes projects and none used sidecars widely. The major benefit of Kubernetes for them was that you could use lots of c
by threeseed 3y ago
I've worked on a lot of very large Kubernetes projects and none used sidecars widely.
The major benefit of Kubernetes for them was that you could use lots of cheap, ephemeral cloud instances to run your platform whilst still having high availability. It ended up saving a ridiculous amount of money.
- hinkley 3y agoHow many services are you running?
- birdiesanders 3y agoHundreds, in my case. We have a sidecar here or there, but essentially our entire operation is run in distroless containers that consume config maps. We have one source of truth for 5 baremetal cloud regions, a number of private on-prem cloud regions, our build and test infrastructure, and nearly everything else, it is our Argo repo and the auto-generated operator manifests from our operator mono-repo. We have a common client library that abstracts our CRDs into easy to consume functions, and in the end using Kubernetes as an API for infrastructure operations does exactly what it should; allows full consistency and visibility on configuration.
- hinkley 3y agoYeah, so you are not in that in between place I was talking about, but you’re arguing with me anyway. You do you, I guess.