One of the perks of dropping ESXi is that I no longer have to navigate the VMWare website. That site is an abomination, with dead ends, login loops, dead links, and a million more issues.
Proxmox isn’t perfect, but it has a lot going for it.
> When asked to comment on this story, a Broadcom representative declined to answer specific questions regarding VMware customers' concerns. Instead, the company referred me to Broadcom CEO Hock Tan's "recent blog posts"
In other words, their answer continues to be "Fuck you, that's why"?
FOr many customer, the amount of time and effort needed needed to migrate from Vmware to some other competitor is just too much so they're stuck in the Broadcom stack and Broadcom knows this. It'll cost them more in labor and man hours than it would to just stay there and swallow the price increases.
We found this to be true for ourselves, however, we did not get hit with anywhere near a 300% price hike. 25-50% maybe. That's not to say we are not profiling the alternatives in the background.
I wonder how much longer we will be hearing different mashups of the VMware saga. I swear this has popped up on my feeds over the past year nearly as much as iPhone 16 speculation has.
It's an ongoing story. The price squeezes just keep coming.
They haven't even finished the last round of squeezes and are planning on more price increases within the next month to force people to lock in or get out.
Has anyone tried to run kubevirt on proxmox. As in bootstrap k8s on debian and manage kvms with k8s yet still retain the option to use proxmox for managing the same kvms
Why not just use Kubernetes on bare metal directly (for example, using Talos https://www.talos.dev/) and install kubevirt on top for non-k8s workloads?
Installing Kubernetes on proxmox would be on bare metal. Proxmox is debian + proxmox packages. My motivation for proxmox is making use of it's ui which kubevirt lacks
Right I'm not suggesting inside a vm or LXC, I mean directly on the debian operating system of the proxmox host. Then kubevirt and proxmox would create vms on the same metal. They are both qemu under the covers
They might be qemu but proxmox does not use libvirt or similar. You won't see VMs created using anything else in the proxmox interface. (This is a simplification. They have a lot of custom things other than not using libvirt.)
One of the perks of dropping ESXi is that I no longer have to navigate the VMWare website. That site is an abomination, with dead ends, login loops, dead links, and a million more issues.
Proxmox isn’t perfect, but it has a lot going for it.
> When asked to comment on this story, a Broadcom representative declined to answer specific questions regarding VMware customers' concerns. Instead, the company referred me to Broadcom CEO Hock Tan's "recent blog posts"
In other words, their answer continues to be "Fuck you, that's why"?
FOr many customer, the amount of time and effort needed needed to migrate from Vmware to some other competitor is just too much so they're stuck in the Broadcom stack and Broadcom knows this. It'll cost them more in labor and man hours than it would to just stay there and swallow the price increases.
We found this to be true for ourselves, however, we did not get hit with anywhere near a 300% price hike. 25-50% maybe. That's not to say we are not profiling the alternatives in the background.
I have seen spikes between 4x to ten fold. I work in a regulated industry.
I wonder how much longer we will be hearing different mashups of the VMware saga. I swear this has popped up on my feeds over the past year nearly as much as iPhone 16 speculation has.
It's an ongoing story. The price squeezes just keep coming.
They haven't even finished the last round of squeezes and are planning on more price increases within the next month to force people to lock in or get out.
Contracts are being renewed over the next couple years yet for clients I'm working with, so probably at least that much longer.
Has anyone tried to run kubevirt on proxmox. As in bootstrap k8s on debian and manage kvms with k8s yet still retain the option to use proxmox for managing the same kvms
Why not just use Kubernetes on bare metal directly (for example, using Talos https://www.talos.dev/) and install kubevirt on top for non-k8s workloads?
Installing Kubernetes on proxmox would be on bare metal. Proxmox is debian + proxmox packages. My motivation for proxmox is making use of it's ui which kubevirt lacks
Installing k8s on a proxmox VM/LXC isnt direct bare metal as it adds the Hypervisor overhead
Btw there is a kubevirt UI
https://kubevirt-manager.io/
Right I'm not suggesting inside a vm or LXC, I mean directly on the debian operating system of the proxmox host. Then kubevirt and proxmox would create vms on the same metal. They are both qemu under the covers
They might be qemu but proxmox does not use libvirt or similar. You won't see VMs created using anything else in the proxmox interface. (This is a simplification. They have a lot of custom things other than not using libvirt.)