Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fix for Policy based volume provisioning failure due to long VM Name in vSphere cloud provider #50722

Merged
merged 1 commit into from
Aug 16, 2017
Merged

Fix for Policy based volume provisioning failure due to long VM Name in vSphere cloud provider #50722

merged 1 commit into from
Aug 16, 2017

Commits on Aug 16, 2017

  1. Using hash/fnv to generate the vmName 

            vSphere has limitation of 80 characters for vmName.
        with vsphere-k8s prefix and "vmdisk.volumeOptions.Name" vmName can become easily bigger than 80 chars.
        Used hash funciton just of the "vmdisk.volumeOptions.Name" part as cleanup dummyVm logic depends on prefix "vsphere-k8s"
    rohitjogvmw committed Aug 16, 2017
    Configuration menu
    Copy the full SHA
    1de7d47 View commit details
    Browse the repository at this point in the history