What we learned after a year on Kubernetes

Re:What we learned after a year on Kubernetes by kkapelon on Thursday September 17, 2020 @08:35AM (#24503823)

So you are saying that Ansible, Chef and puppet are fads? That solve no real problems?

OpenMosix, Bewolf and Grid computing were mostly confined on research circles. I never saw them took off like K8s did.

So comparing K8s with OpenMosix is a bit unfair...

[ Parent | on HN ]

Re:What we learned after a year on Kubernetes by pjmlp on Thursday September 17, 2020 @09:10AM (#24504153)

I am saying that apparently they are not good enough for the Kubernetes generation.

Eventually there will come the post-Kubernetes generation and the cycle does yet another turn.

[ Parent | on HN ]

Re:What we learned after a year on Kubernetes by Keycap on Friday September 18, 2020 @05:02AM (#24514568)

'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?

[ Parent | on HN ]

Re:What we learned after a year on Kubernetes by pjmlp on Saturday September 19, 2020 @04:35AM (#24526073)

What paradigm shift and what novelty?

My first containers were called HP-UX Vaults in 1999.

The cycle continues its reboot.

[ Parent | on HN ]

Re:What we learned after a year on Kubernetes by Keycap on Monday September 21, 2020 @03:14AM (#24540675)

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.

[ Parent | on HN ]