fix: use none driver without sudo in upstream minikube e2e tests #572
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of the change:
Similar to operator-framework/operator-lifecycle-manager#1983, we started seeing failures in the minikube e2e tests after the underlying
ubuntu-latest
VM image used in github actions changed from ubuntu 18 to 20.It seems like using
minikube config set vm-driver none
is no longer being respected, minikube used the docker driver instead and complained about sudo mode. This change is to use thenone
vm driver for and not require sudo for running minikube. Based on kubernetes/minikube#3760 this seems to work now and will be supported.Motivation for the change:
Regression
Reviewer Checklist
/docs