3 ms·
Glad I'm not the only one who almost got white-whaled into running stateful services on K8s. The API is so slick that it makes you feel you can do anything. Bu
by elsonrodriguez 7y ago
Glad I'm not the only one who almost got white-whaled into running stateful services on K8s.
The API is so slick that it makes you feel you can do anything. But there's can, and there's should.
- pas 7y agoThe API is there, but is there a stable MongoDB Operator? ( https://github.com/Ultimaker/k8s-mongo-operator https://github.com/Ultimaker/k8s-mongo-operator ? https://github.com/mongodb/mongodb-enterprise-kubernetes https://github.com/mongodb/mongodb-enterprise-kubernetes ? )
- elsonrodriguez 7y agoHonestly I'd only think of running Mongo on Kubernetes if my organization is thoroughly bored with how well they've managed Mongo upgrades, scaling, outages, migrations, and tuning over the last year on a traditional VM setup. Even so, if everyone's bored with the stability, why change it? I'm an advocate for databases in dev/test environments on K8s due to ease of deployment, but there's too many moving pieces around storage for it to be a great idea for production out the gate.
- pas 7y agoWell. The benefits (monitoring, telemetry/observability) are nice enough that I might think about running it on k8s in prod. But only after sufficient number of dev/staging clusters have been sacrificed.