What we learned after a year on Kubernetes

Re:What we learned after a year on Kubernetes by secondcoming on Thursday September 17, 2020 @07:34AM (#24503354)

> Developers don't want a VM and you can't manage and maintain VMs if someone else is doing something with them.

I want a VM because I want my dev environment to exactly replicate the production environment, down to the kernel. It also means that if I leave my employer I can just delete my VM on my personal machine.

We've also not had any issues with maintaining production VMs, our release pipeline packages up our code into a debian package and them creates a VM image from that. This is then deployed across all regions. If you need to roll back just deploy the previous VM image version. GCP handles killing old instances and starting new instances for you.

[ Parent | on HN ]

Re:What we learned after a year on Kubernetes by kkapelon on Thursday September 17, 2020 @09:01AM (#24504062)

>We've also not had any issues with maintaining production VMs, ... If you need to roll back just deploy the previous VM image version. ...

We've also not had any issues with breeding horses....If I just need to go somewhere I just ride my horse...

I don't see any value in cars(k8s). They are complex (oil changes, fuel consumption etc...)

[ Parent | on HN ]

Re:What we learned after a year on Kubernetes by Keycap on Thursday September 17, 2020 @07:40AM (#24503393)

I did not talk about your specific use case.

Feel free to be happy with your setup.

Also i'm not able to determine if your setup would still be much better (faster, easier to maintain etc.) if you would set completly on containers instead of a VM as i'm not aware of your workload at all.

[ Parent | on HN ]

Re:What we learned after a year on Kubernetes by auspex on Thursday September 17, 2020 @08:37AM (#24503848)

Having the application run the same in dev as in production is one of the main selling features of a containerized environment.

[ Parent | on HN ]

Re:What we learned after a year on Kubernetes by secondcoming on Thursday September 17, 2020 @08:58AM (#24504026)

As far as I'm aware containers do not replace the kernel, only userland.

[ Parent | on HN ]

Re:What we learned after a year on Kubernetes by kkapelon on Thursday September 17, 2020 @09:04AM (#24504096)

This is of course important but only for people who actually need this guarantee.

Yes if you are developing C/C++/Assembly then Kubernetes/containers might not be for you.

But for several other companies (e.g. Java users) the kernel version is not important.

So we are back to same argument. Just because that you personally don't see value in something, doesn't mean that it is a fad.

[ Parent | on HN ]

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

Java users are doing just fine with application containers.

[ Parent | on HN ]

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

That is a whole different discussion. If by application container you mean Tomcat then maybe. But if you mean Weblogic or Oc4j or WebSphere then hell no :-)

Then maybe you agree that Kubernetes brought some advantages that until recently only Java devs enjoyed to the rest of the world (PHP, Python etc)?

[ Parent | on HN ]

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

Yes I mean WebSphere.

Kubernetes is a kludge to solve problems that should be sorted out by the respective language communities.

Then there is the whole issue that interpreters without JIT/AOT should only be used for scripting.

[ Parent | on HN ]

Re:What we learned after a year on Kubernetes by secondcoming on Thursday September 17, 2020 @09:21AM (#24504265)

> Just because that you personally don't see value in something, doesn't mean that it is a fad

GP is the one who made blanket statement 'developers don't want a VM', not me.

[ Parent | on HN ]