Menu

5 Gotchas from Building an OpenShift Virtualization Lab
📰

5 Gotchas from Building an OpenShift Virtualization Lab

DEV Community: kubernetes·Gaganpreet Singh·12 days ago
#8tTdl6W5
#devtokubernetes#devto#dev#project#vddk
Reading 0:00
15s threshold

Every chapter of The Lab Manual has GOTCHA boxes: problems I actually hit while building the lab, with the real error and the fix. These five cost me the most time.

1. Public DNS can't see your cluster

The bastion started out with public DNS servers. Public DNS can't resolve your internal cluster names, so openshift-install wait-for and oc couldn't find api.<cluster>.<domain> .

Fix: point the bastion at the internal DNS servers that hold the cluster records.

nmcli connection modify <nic> ipv4.dns "<dns1> <dns2>" nmcli connection up <nic> dig +short api.<cluster>.<domain>

Enter fullscreen mode

Exit fullscreen mode

2. No VDDK = slow

Without VDDK, MTV reads disks over HTTPS through vCenter. My 10 GiB test VM took 61 minutes to copy. The log line that gives it away is nbdkit: curl .

Fix: build a VDDK image and set vddkInitImage on the provider. Full walkthrough in part 3 of this series, "VDDK vs No VDDK".

3.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.