4 ms·
The problem is that a k8s cluster requires hundreds/thousands of lines of yaml configuration just for the core components, including a choice of network overlay
by developer2 8y ago
The problem is that a k8s cluster requires hundreds/thousands of lines of yaml configuration just for the core components, including a choice of network overlay. Everybody copies the same default configs hoping they will work out of the box, without understanding how each option actually affects the cluster. Add to this the container and yaml upgrades that should be applied per component every month or so, and it's nigh impossible for most companies to handle.
Kubernetes is far too complex to set up from scratch. The only way to reduce the complexity – or rather, to offload it – is to use managed Kubernetes via AWS or GCE. The fact that using AWS or GCE is effectively the only viable method for running a production Kubernetes cluster speaks volumes to how non-simple the stack truly is.
- jamougha 8y agoKubernetes used to be hard to set up from scratch. Recently we had to set up a new cluster and it just worked with very little faff.
- neop1x 8y agoNew kubeadm makes is easier to set up a cluster from scratch. But the complexity truly is there and it's difficult to understand all parts of it. But - clusters are complicated. Running hundreds of workload jobs in a manageable way shouldn't be easy, right? Maybe it is not a problem of k8s but the fact is we now require complicated stack with many moving parts and it is not easy to manage it reliably.
- brimstedt 8y agoI can recommend Kubernetes the right way [0] as a way to get started with your own k8s setup from scratch in a controlled manner. 0: https://github.com/amimof/kubernetes-the-right-way/blob/master/README.md https://github.com/amimof/kubernetes-the-right-way/blob/mast...