Four years after its release, Kubernetes has come a long way

Re:Four years after its release, Kubernetes has come a long way by iampims on Wednesday June 06, 2018 @05:47PM (#17251381)

    I felt like if anything went wrong I'd be in a world of hurt trying to debug it.

This is the part very few k8s aficionados mention: how complicated is it to troubleshoot when something goes wrong?

[ Parent | on HN ]

Re:Four years after its release, Kubernetes has come a long way by barrkel on Wednesday June 06, 2018 @07:08PM (#17251908)

The core k8s, not that bad, once you've learned where to look - logs on pods, events, and kubelet logs from journalctl. That last one is important not to forget when debugging plugin controllers.

[ Parent | on HN ]

Re:Four years after its release, Kubernetes has come a long way by geggam on Wednesday June 06, 2018 @06:10PM (#17251518)

Not to mention when folks talk HA and you ask about federation they just give you a blank stare.

k8s is HA in the same region if you are using GKE. Not really what you can call HA

[ Parent | on HN ]

Re:Four years after its release, Kubernetes has come a long way by pests on Wednesday June 06, 2018 @06:56PM (#17251830)

Google just posted a blog[0] about multi-region clusters and ingress.

It's a little hacky as you need to create multiple clusters in each zone/region and then with an anycast IP attached to a Google Cloud Load Balancer.

[0] https://cloudplatform.googleblog.com/2018/06/How-to-deploy-g...

[ Parent | on HN ]

Re:Four years after its release, Kubernetes has come a long way by geggam on Wednesday June 06, 2018 @07:00PM (#17251856)

Hacky is not production ready.

[ Parent | on HN ]

Re:Four years after its release, Kubernetes has come a long way by pests on Wednesday June 06, 2018 @10:12PM (#17252728)

Its not hacky in that sense. They provide a new kubemci tool and I'm sure it will be given the k8 release treatment.

[ Parent | on HN ]