3 ms·
Why bother locking in when Kubernetes operators and resources can deploy and maintain the lifecycle of common services? Why would I want some old, forked versio
by birdyrooster 7y ago
Why bother locking in when Kubernetes operators and resources can deploy and maintain the lifecycle of common services? Why would I want some old, forked version of elasticsearch (for example) when I can have the latest version automatically provisioned and scaled with high availability?
What is the AWS value add as Kubernetes operators become mature? They own datacenter space and have contracts for power and internet.
- Aeolun 7y agoI think you answered your own question. > As kubernetes operators become mature This implies (and I agree) that they’re not mature yet. Aside from that, there is still more to maintain on kubernetes than on AWS. Those pods don’t patch themselves...
- birdyrooster 7y agoI agree we are in a transition period and that more maturity is needed for penetration but we are already underway. If you are an executive planning for the next 5 years, this is one of your goals for your engineering organization.