Re:Kubernetes reinvented virtual machines in a good sense
by k8sToGo on Sunday July 31, 2022 @06:02PM
(#32299284)
I don't know about your team, but in our team I try to move as much as possible to kubernetes so I have a common way of deployment across all members. Of course if you are just thrown into the cold water without help from the Kubernetes guys, it will suck.
Also I noticed that once developers "get it", they actually like it a lot.
Re:Kubernetes reinvented virtual machines in a good sense
by Already__Taken on Sunday July 31, 2022 @05:51PM
(#32299205)
> while it was tedious to develop, mostly because I cannot run docker on my work PC
Have a look at tilt.dev You can get it to build in-cluster too so you only need the CLI. I've really enjoyed its workflow.
Or try podman-remote. Should be easier to get those CLI tools on your work PC.
Re:Kubernetes reinvented virtual machines in a good sense
by CameronNemo on Sunday July 31, 2022 @05:53PM
(#32299221)
Our k8s based deployments go so much smoother than our VM based deployments (Ansible). We have centralized logging set up for k8s, but not VMs. We have post-update health checks for k8s pods, but not systemd services. Et cetera.
Re:Kubernetes reinvented virtual machines in a good sense
by orwin on Wednesday August 03, 2022 @08:51AM
(#32331012)
I understand that. But i already have the code to set up logging and health checks (i basically took the code i did at my previous work, it was open source so no issue here).
Like i said, it is fine, i'm not mad about it, it took some time to understand but i get it now and while still less efficient, i'm way better at it, and when i finish this project the next one will be easier. Also, it is important that the whole team use the same product: it was a good reason to loose one man-month to get me up to date with the rest of the team and facilitate my next "app".
Re:Kubernetes reinvented virtual machines in a good sense
by sporkland on Sunday July 31, 2022 @06:08PM
(#32299327)
Why can't you run docker on your work PC? If it's the licensing issues I'd recommend using lima-vm (https://github.com/lima-vm/lima) as a substitute.
I don't think this is that bad tbh. I runs my unit tests on container construction and while it was tedious to develop, mostly because i cannot run docker on my work PC, i understand that it makes it easier to inventory and check the advancement. The management will always love it, so i think kubernetes is here to stay. Not because it solve a lot of engineering issues (not for me anyway, i'd rather run a cron in my VM than declare a kube cronJob), but because it solve a lot of other fondamental issues for the management (inventory, visibility on existing/running projects. And everybody use the same system without using the _same_ system.)