Not understanding how k8s work, or actual provider screwing up?
if the former - I try to read carefully and test my workloads in a test cluster before I do it in prod.
if the latter, I think google has excellent operational excellence.
This is like saying you wouldn't take driving advice from me until I total a few cars. Perhaps I didn't total a few cars because I make good driving decisions?
>>This is like saying you wouldn't take driving advice from me until I total a few cars
No, I am saying you do not have enough experience with k8s. That is all. Totaling a car implying you are driving, using k8s implying that whoever wrote that particular part of k8s is driving. You have some control but ultimately you need to understand what is going on. As that list shows many companies who put k8s into production learned it in a hard way.
Should I compile a list of failure stores for companies that ran Linux because Linux is complicated or has had various bugs?
How about a list of failure stories of how Ruby causes problems?
You can get errors with any system. You would need to prove to me that k8s has say more errors per day than a competitor (lambda? VMs). I just don’t understand...
This is the claim that you made. I would argue that since you do not have experience with it you perceive it as you do not need to focus on your infra. Once you run into a failure with k8s and you actually need to fix it, this might change. That is all.
I have run into Linux failures. I still use Linux.
I have ran into bugs in Java. I still use Java when it makes sense.
So not sure what you are trying to get to. You give up on a technology the first time you have a problem?