- 60% of the Kubernetes ecosystem is half-baked alpha software
- Maintaining 200+ clusters for 10 small applications
- Cloud bills
- Autoscaling never working well
- Trying to untangle Terraform state without taking down Prod
- Maintaining 200+ clusters for 10 small applications
- Cloud bills
- Autoscaling never working well
- Trying to untangle Terraform state without taking down Prod
1. I don't know about any of this; we don't seem to have problems.
2. This sounds like an architecture issue, not a k8s issue.
3. Our entire GKE infrastructure costs less than $50 a month.
4. You're right here; it doesn't work 'well', but it works 'well enough' for our use cases.
5. I'm sure you're talking about some event that was far more complex than the few times we've had to drain our pool, but we did what we needed to do without downtime in production. While annoyingly esoteric, I thought it worked pretty fucking well compared to our alternatives.
We are running many hundreds of jobs on those peak days with only a handful running on any other day. While many bring up examples where 24/7 infrastructure from a single box is more than plenty, we find that we can run micro VMs in this configuration and not have to worry about resource contention as our jobs run.
Pre-GKE, we were managing the timing manually, which was fine until we started to scale, but we found this to be a far better situation. Particularly because we simply don't have to think about it.
YMMV.
Uhhh what? I mean even my personal DO based cluster runs about $40 a month. I'm skeptical a production cluster is at $50.
Service Compute Engine Kubernetes Engine
Cost. $191.78 $62.34
Discounts ($13.96) ($62.34)
Promotions and others $0.00 $0.00
Subtotal $177.83 $0.00
We are an ESOP so, as employee owners, it behooves us to be as cost-conscious as possible.
At this scale, you don't need Kubernetes, invest in a pocket calculator instead.
This one is fair. Wasted a lot of time trying to find the "correct" dependencies—I remember the Nginx Ingress Controller specifically being a headache—only to find a maze of deprecations, poorly written documentation, or stuff that just flat out didn't work. That was ~18 months ago (I set up my cluster to run sites for my business and have basically left it alone) so things may have changed but at the time I remember being surprised after hearing so much hype.
Primarily because there was very little obscurity (i.e., config files that automate away a lot of thinking or Dockerfiles/containers doing the same). It also left me feeling more confident about stability because if something isn't working, it's pretty clear what I broke/forgot. Worst "bug" I ran into was a snap server hanging when installing a dependency.