Meta. Is this a common usage of .af domains?
Kubernetes Failure Stories
21–30 of 203 posts
Re: Kubernetes Failure Stories
#22Meta. Is this a common usage of .af domains?
I only came here to comment that the domain name was fantastic for this usage.
Re: Kubernetes Failure Stories
#23Re: Kubernetes Failure Stories
#24The current trend goes to multi-cluster environments, because it's way too easy to destroy a single k8s cluster due to bugs, updates or human mistake. Just like it's not an very unlikely event to kill a single host in the network e.g. due to updates/maintenance. For instance, we had several outages when upgrading the kubernetes version in our clusters. If you have many small cluster it's much easier and more save to…
Sounds like madness. Should we expect a new tool that orchestrates all of your Kubernetes clusters?
Re: Kubernetes Failure Stories
#25The Istio one hits home. It is the single scariest thing to work with in our kubernetes clusters. We've caused several outages by changing the smallest things.
Re: Kubernetes Failure Stories
#26These are great, I found myself trying to predict the related areas, “..Slow connections..” ooh that must be conntrack! Been burnt by kube2iam too.. I guess it’s k8s failure bingo.
Re: Kubernetes Failure Stories
#27Earlier quoted context omitted.
A Kubernetes for Kubernetes! But what about when we want to upgrade that?
I mean thats simply Kubernetes for Kubernetes for Kubernetes. Lets go!
I need a Kubernetes Kubernetes Kubernetes Kubernetes Kubernetes emulator so I can run Civilization 14 on my iPhone 35XSXS.
Re: Kubernetes Failure Stories
#28The current trend goes to multi-cluster environments, because it's way too easy to destroy a single k8s cluster due to bugs, updates or human mistake. Just like it's not an very unlikely event to kill a single host in the network e.g. due to updates/maintenance. For instance, we had several outages when upgrading the kubernetes version in our clusters. If you have many small cluster it's much easier and more save to…
Sounds like madness. Should we expect a new tool that orchestrates all of your Kubernetes clusters?
It used to be called Ubernetes, shame that name didn't stick.
Re: Kubernetes Failure Stories
#29The current trend goes to multi-cluster environments, because it's way too easy to destroy a single k8s cluster due to bugs, updates or human mistake. Just like it's not an very unlikely event to kill a single host in the network e.g. due to updates/maintenance. For instance, we had several outages when upgrading the kubernetes version in our clusters. If you have many small cluster it's much easier and more save to…
Sounds like madness. Should we expect a new tool that orchestrates all of your Kubernetes clusters?
I operate one at work, actually. It's not so bad.
Re: Kubernetes Failure Stories
#30The current trend goes to multi-cluster environments, because it's way too easy to destroy a single k8s cluster due to bugs, updates or human mistake. Just like it's not an very unlikely event to kill a single host in the network e.g. due to updates/maintenance. For instance, we had several outages when upgrading the kubernetes version in our clusters. If you have many small cluster it's much easier and more save to…
Sounds like madness. Should we expect a new tool that orchestrates all of your Kubernetes clusters?
> There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult.
- C. A. R. Hoare