4 ms·
You either recreate a less reliable version of kubernetes for workload ops or you go all in on your cloud provider and hope they'll be responsible for your dest
by candiddevmike 3y ago
You either recreate a less reliable version of kubernetes for workload ops or you go all in on your cloud provider and hope they'll be responsible for your destiny.
Vanilla Kubernetes is just enough abstraction to avoid both of those situations.
- x86x87 3y agoYou cannot really be cloud agnostic these days - even when using k8s. So learning to use the capabilities the cloud provides is key.
- p_l 3y agoDoesn't really mesh with my experience, especially the longer k8s been out. It can be cheaper to depend on cloud provider to ship some features, but with tools like crossplane you can abstract that out so developers can just "order" a database service etc. for their application.
- PUSH_AX 3y agoIs “hope” the new replacement for SLAs? Or am I missing something with that statement?
- k8sToGo 3y agoSLA do not prevent something from breaking, unfortunately. It is just a blame construct.
- p_l 3y ago"Hope" that your cloud provider matches as well your needs as you thought, that vendor lock-in doesn't let them milk you with high prices, etc. etc. None of that is prevented with SLA
- PUSH_AX 3y agoThis requires the same skill and experience as figuring out if k8s is going to be a good fit. Arguably if you can’t evaluate the raw cloud offerings and jump on a supposed silver bullet you need to stop immediately.
- p_l 3y agoAt this point I found out that k8s knowledge is more portable, whereas your trove of $VENDOR_1 knowledge might suddenly have issues because for reasons outside of your capacity to control there's now big spending contract signed with $VENDOR_2 and a mandate to move. And with smaller companies I tend to find k8s way more cost effective. I pulled things I wouldn't be able to fit in a budget otherwise.