Kubernetes Failure Stories

Post by bpicolo » Sun, Jan 20, 2019, 10:03 PM UTC

jacques_chester wrote: post #79

cygned wrote: post #49

I am a developer and I find k8s frustrating. To me, its documentation is confusing and scattered among too many places (best example: overlay networks). I have read multiple books and gazillions of articles and yet I have the feeling that I am lacking the bigger picture. I was able to set it up successfully a couple of times, with more or less time required. Last time, I gave up after four days because I realized tha…

Kubernetes has always had an identity crisis. Who is aimed at, app developers or platform operators? Clear, obvious contracts between the two roles are valuable, even if you decide to combine them. I'm moderately hopeful that Knative will help in that regard, as it is more conclusively oriented towards the developer. But I am wary that since it leaves the implementation details completely visible, it may not achieve…

Post by karakanb » Sun, Jan 20, 2019, 10:03 PM UTC

tyingq wrote: post #43

dvnguyen wrote: post #21

Having used Docker Compose/Swarm for last two years, I remember having problems with them twice. One of which was an MTU setting which I didn't really understand why, but overall I was relatively happy with them. Since Kubernetes seems to have won, I decided to learn it but got some disappointments. The first disappointment is setting up a local development environment. I failed to get minikube running on a Macbook A…

Digital Ocean's K8S offering is out of beta now: https://www.digitalocean.com/products/kubernetes/

Post by sonnyblarney » Sun, Jan 20, 2019, 10:19 PM UTC

m0zg wrote: post #100

sonnyblarney wrote: post #97

Earlier quoted context omitted.

"a lot of techies live in areas with exorbitant cost of living," And what do you think is the primary driver of said cost of living? I believe there is a ton of arbitrary complexity in the system, and though it's not specifically created, it definitely grows if it's not checked and entities with power have no reason to do that. Google, Oracle, MS, Governments, Banks - have very little incentive to clear the weeds, us…

>> And what do you think is the primary driver of said cost of living? Mostly NIMBY-driven refusal to build more housing and transportation infrastructure. It's not like the US is lacking for land. There's no reason a dilapidated teardown-ready shack should cost $2M, no matter where it is.

Post by parasubvert » Sun, Jan 20, 2019, 10:22 PM UTC

jcoffland wrote: post #55

parasubvert wrote: post #44

Earlier quoted context omitted.

It’s common to pay for things to make them easier to configure/manage. Red Hat OpenShift on RHEL, Pivotal Container Service on Ubuntu, Red Hat’s nextgen CoreOS based Kubernetes, Canonical’s Charmed Kubernetes Distribution on Ubuntu, etc. all have different config management , install, upgrade, patching mechanisms that vary from Ansible, to Terraform, to BOSH, to Juju. Some handle PXE bare metal, some don’t. Etc. Ther…

> It’s common to pay for things to make them easier to configure/manage. Yes but in the case of RedHat specifically those goals are not achieved.

Post by lmm » Sun, Jan 20, 2019, 10:38 PM UTC

jordanbeiber wrote: post #91

lmm wrote: post #87

Earlier quoted context omitted.

> If you achieve this scale of teams suggested, it means you have a lot of implicit gains here as well, right? > Such as higher quality, higher "velocity", separation of concern and hopefully a clear sense of ownership. No, it means you pay a huge overhead. Quality and velocity both drop as your day-to-day development requires a lot more setup and faff to do anything, and counterintuitively so does separation of conc…

Which is why you’ll need the input and help from experienced sysadmins that like to do development, which actually is ”automation”. This done right reduces overhead and gives you an edge in repeatability and quality. Both are required to scale.