What we're seeing is a failed provisioning error when adding volumes, we hit this closed issue:
https://github.com/kubernetes/kubernetes/issues/58927 Kubernetes behaviour changed to fix this issue by switching to the */product_serial file as the source of truth.
But for our case the product_serial was incorrect, and the product_uuid was the source of truth, this meant when Kubernetes went to get the node it failed to find the VM: https://github.com/kubernetes/kubernetes/blob/103e926604de6f79161b78af3e792d0ed282bc06/staging/src/k8s.io/legacy-cloud-providers/vsphere/vsphere_util.go#L656
What we're seeing is a failed provisioning error when adding volumes, we hit this closed issue:
https:/ /github. com/kubernetes/ kubernetes/ issues/ 58927 Kubernetes behaviour changed to fix this issue by switching to the */product_serial file as the source of truth.
But for our case the product_serial was incorrect, and the product_uuid was the source of truth, this meant when Kubernetes went to get the node it failed to find the VM: /github. com/kubernetes/ kubernetes/ blob/103e926604 de6f79161b78af3 e792d0ed282bc06 /staging/ src/k8s. io/legacy- cloud-providers /vsphere/ vsphere_ util.go# L656
https:/