Saustrup

After having been almost exclusively on the platform level of #Kubernetes for half a decade, it's definitely a change of scenery to be helping #Java developers moving legacy stuff from VMs to containers.

Today I went down the rabbit hole to investigate Java 8 container resource awareness. As expected, the support was spotty and outdated, requiring the old #cgroups v1. With a bit of hacking, if should be possible to add the proper parameters at runtime though, preventing the memory hungry Java container from the dreaded #OutOfMemory or OOM kill.

I miss having more control over the #platform, but that's not in the cards this time around.

May 20 at 1:06pmWeb
Show threadDamienMay 20
@saustrup curious what makes you avoid k8s for this case? (Or maybe what makes someone else enforce that requirement?)
Show threadSaustrupMay 20
@damien I'm not avoiding Kubernetes here? We're moving workloads to Kubernetes. We're just having some issues with the old Java 8 JVM.
Show threadDamienMay 20
@saustrup ah, sorry for misunderstanding. I read it as moving from VM to containers *outside of Kubernetes*.
Show threadElricMay 20
@saustrup Why are people running Java 8 in production? That's like 12 years old.
Show threadSaustrupMay 20
@elricofmelnibone Very conservative people running very conservative workloads for very conservative clients.