-
Notifications
You must be signed in to change notification settings - Fork 3.3k
Temporary pin minikube to 1.2.0 due to regression in 1.3.0 #918
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
Temporary pin minikube to 1.2.0 due to regression in 1.3.0 #918
Conversation
b0400cc
to
fee1dff
Compare
I'm watching kubernetes/minikube#5014. I think we are running into the same problem. |
/lgtm |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: roycaihw, yliaog 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 |
fee1dff
to
d300fd7
Compare
New changes are detected. LGTM label has been removed. |
Added a comment. Retagging |
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.
@roycaihw I believe such regressions will occure once in a while. I would remove v1.2.0 in favour of a variable, which for now can be set to 1.2 and late back to latest.
No description provided.