Overview
In this article, I’m discussing differences I’m finding as I upgrade my four Kubernetes environments from 1.25 to 1.36.
To Start
The articles I wrote 4 years ago were for 1.25. As I built the clusters, I stumbled into issues and problems and I documented what I found.
Back then I was on a VMware cluster. Since the Broadcom purchase of VMware, I’ve lost access to purchase a learning license so I’ve had to either migrate over to KVM/Qemu, which I already have terraform plans and ansible scripts for, or step up and give Proxmox a try again.
I’ve used Proxmox in the past and since I had VMware, it wasn’t as polished as VMware so I let it slide. At one job I was using KVM/Qemu to manage builds so I turned to that.
I’ve attempted a KVM/Qemu build in the past and wasn’t very successful, but it was also before terraform and providers so going back to it due to a job, was interesting and I took one of my R710 servers and tried replicating my home servers using terraform and cloud-init. It worked well enough.
A new job was running Proxmox so I thought I’d give it a try again. I have an environment already running so I can leverage the configuration and move forward at home, especially with the loss of the VMware environment.
Today
So here we are. I’m going to rebuild my environment to 1.36 and while doing so, upgrading my 1.25 articles here to reflect those changes. I won’t be documenting the changes, unless it’s interesting. And this article is more explaining the migration. Folks might have been using the 1.25 articles so I thought I’d make sure they understood (if any) the changes.