Live data from Hacker News

What we learned after a year on Kubernetes

about.gitlab.com

161–162 of 162 posts

Re: What we learned after a year on Kubernetes

#161

Earlier quoted context omitted.

It must not fit your use case and that is ok. Kubernetes is made for the people that have to run your systems and keep them operational (ops/devops). It makes our lives a billion times easier on two fronts. Disclaimer, I am referring to a managed solution like GKE, I can imagine running k8s on your own hardware would be harder. Uptime & Stability: autoscaling, health checks, replacing nodes, restarting containers. Th…

I'd like to hear more on troubleshooting with a managed k8s platform and how you diagnose such issues. My organization is playing with EKS and while perhaps it is different from GKE I feel like I have minimal visibility into if the control plane is healthy. I've had several instances where all of my node groups have become unhealthy for various reasons and EKS failed to spin up new nodes to resolve the issue.

@wronglebowski In EKS there is a logging option for the control plane, turn this on and you get all the control plane logs in Cloudwatch logs.

Re: What we learned after a year on Kubernetes

#162
post #160
post #156

Earlier quoted context omitted.

'Not good enough'? Do you now think progress is bad? Ansible and co did and still do a great job. kubernetes is not just a thing, its also a paradigma shift. It sounds like something new is just bad because its new?

What paradigm shift and what novelty? My first containers were called HP-UX Vaults in 1999. The cycle continues its reboot.

It doesn't.

Its getting refined, standardized and widely used.

k8s for me is the shift to a declarative infrastructure. Easy to put in your source code repository.

Also as a goody you get industry leaders offering a certified k8s experience.

And all of it is opensource and free.

A fully platform independent orchestration platform.

Post reply on HN