clcollins reported a new issue against the project: `atomic-wg` that you are following:
``
The vSphere Cloud Provider for Kubernetes/OpenShift requires that "disk.EnableUUID =
True" be set for the node VMs to be able to identify the dynamically provisioned
VMDKs that are mounted into the containers for dynamically created persistent storage
volumes. (See:
https://kubernetes.io/docs/getting-started-guides/vsphere/#enable-vsphere... ;
and:
https://docs.openshift.org/latest/install_config/configuring_vsphere.html...)
Setting "disk.EnableUUID = True" allows disks to show up in /dev/disk/by-uuid
when they're added to the VM.
We can set it manually each time we create a new node, but the potential to forget is
high, and the consequences would be unfortunate (pods would no longer be able to mount
storage when scheduled on nodes without the setting).
Considering a lot of the focus on Atomic Host is for Kubernetes & OpenShift, and folks
using the vSphere OVA for Atomic would probably like to use the vSphere provisioning with
it, this might make sense to be a default setting.
Ideally this would apply to the Red Hat and CentOS Atomic OVAs as well.
Included for more info:
I asked about this in the #Atomic channel, and the replies mentioned -
(03:10:36 PM) walters: it's going to involve changes to
https://github.com/redhat-imaging/imagefactory/ most likely
(03:11:35 PM) walters: specifically
https://github.com/redhat-imaging/imagefactory/blob/master/imagefactory_p...
I believe
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/431