-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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.
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
Add new VMware unified driver to supported list #2606
Conversation
Can one of the admins verify this patch? |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: frapposelli Assign the PR to them by writing The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/assign @luxas |
We shouldn't really add this to an officially supported list until we get automated integration testing for it. @minikube-bot OK to test |
@dlorenc we’re working on getting a CI environment to test integration under the driver repo. |
@frapposelli glad to hear about that last part... :-D |
@dlorenc @gbraad it’s going to take some time to have the environment provisioned, in the meantime, this driver is fixing several issues with our platforms, and extending support to Windows and Linux. Adding support for this and deprecating the docker-machine builtin one should be a priority in order to have better supportability and timely fixes. |
@frapposelli I definitely understand that, but I'm going to have to stay firm on this one. The vmware fusion driver shouldn't have been added without CI tests in the first place, and it's much harder to delete something once it's been merged in. Once we get CI running, we can add this driver. |
I also understand, but have to agree with @dlorenc. |
Understand, let's leave this open and I'll try to speed up with the CI infra on our side. |
Any updates on getting this into the test infrastructure? |
@dlorenc we’re still waiting on the capacity we requested. Shouldn’t take long |
any updates? |
Yes, we have secured the capacity and we're working on setting up CI, this week there's Kubecon (pretty much our the entire team is here) so I would expect to have something ready by end of next week. |
What's the progress on this? |
Unfortunately the CI work was re-prioritized a few times, we’re now working to have the vSphere capacity added to the tide pool, after that is done we can run tests and merge this. |
@frapposelli Thanks for the update! Keep up the great job 🎉 |
Any news on this? |
Sorry guys, this is taking a little longer than expected. /cc @akutz FYI |
@frapposelli: GitHub didn't allow me to request PR reviews from the following users: FYI. Note that only kubernetes members and repo collaborators can review this PR, and authors cannot review their own PRs. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also need to update pkg/minikube/constants/constants.go
to add vmware
to SupportedVMDrivers
.
The changes to the vendor
should be backed out.
@frapposelli This PR needs rebase. |
Do you mind addressing the merge conflicts? I'd like to see about merging this if it's still viable. My apologies for the unnecessarily long delay in reviewing this PR. |
@tstromberg thanks, let me look into it |
@tstromberg the original fork was deleted, created #3534 as a follow up from this PR, which I'm closing |
This PR adds the new VMware unified driver to the supported list, the driver now supports Fusion and Workstation across Windows, Linux and macOS.
A deprecation note has been added for the bundled
vmwarefusion
driver.Ref: #2118 #2526 machine-drivers/discussion#5 machine-drivers/docker-machine-driver-vmware#1
Fixes: machine-drivers/docker-machine-driver-vmware#1 #2118