OKD4 on Proxmox is doable, but the official docs assume bare metal or a cloud. On Proxmox you’ll hit UEFI boot quirks, DNS that breaks the cluster, and storage that won’t provision. Here’s what actually works.

Create the VMs with the right settings
OKD4 needs three control plane nodes and at least two workers. In Proxmox, create each VM with 4 vCPUs, 16GB RAM, and 50GB disk. The catch: use SeaBIOS, not OVMF/UEFI. OKD’s CoreOS image boots fine with SeaBIOS and you avoid the whole UEFI partition mess. Set the NIC to virtio and attach it to a bridge that has outbound internet.
For the OS disk, import the Fedora CoreOS QEMU image. You can grab it from the OKD release page. Don’t use the cloud image—it’s missing the Ignition config hook. Once imported, attach the Ignition config as a config drive (a small ISO with config.ign). I’ve covered a similar flow for Fedora CoreOS on Proxmox.
Networking: DNS is the silent killer
OKD nodes must resolve each other by hostname. Proxmox’s default DNS won’t cut it. You need a local DNS server (dnsmasq or Pi-hole) with A records for api.okd4.example.com, *.apps.okd4.example.com, and each node. Or just edit /etc/hosts on every node—ugly but works for a homelab.
Also, set the cluster network CIDR to something that doesn’t overlap with your LAN. Default is 10.128.0.0/14; if your home network uses 10.x, change it in install-config.yaml before generating Ignition files.

Storage: local volumes need a provisioner
OKD expects a dynamic storage class. On Proxmox, you can use the local-path-provisioner or set up NFS. For NFS, export a share from your Proxmox host or a TrueNAS box, then create a StorageClass with the NFS provisioner. Without this, PVCs stay pending forever.
If you’re already running TrueNAS, check mounting storage in Proxmox for the basics.
Install and bootstrap
Boot all VMs. The control plane nodes will run the bootstrap process automatically. Watch the logs with journalctl -u bootkube on the bootstrap node. Once the API comes up, remove the bootstrap node and approve the worker CSRs.
It’s not plug-and-play, but it’s not rocket science either. The official docs skip the Proxmox-specific bits—UEFI, DNS, storage—and that’s where people get stuck. Fix those three and the rest is just waiting.