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.

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

version: consider moving to 1.0 #2995

Closed
philips opened this issue Jul 19, 2018 · 7 comments
Closed

version: consider moving to 1.0 #2995

philips opened this issue Jul 19, 2018 · 7 comments
Assignees
Labels
area/build-release kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.

Comments

@philips
Copy link
Contributor

philips commented Jul 19, 2018

minikube has been a recommended stable tool for many releases of Kubernetes. Is there any reason to not start making 1.0+ releases? Maybe even tracking Kubernetes releases?

If not what are the milestones for doing that?

@dlorenc
Copy link
Contributor

dlorenc commented Jul 20, 2018

Nope, we should probably bump to v1 soon. I think tracking k8s would be a bit confusing because each version of minikube tends to support several k8s versions, though.

@afbjorklund
Copy link
Collaborator

But even "kubeadm" is still in beta, so I am not sure that minikube is in a more stable state ?
I think it was only "localkube" that came in kubernetes versions, not the minikube tool itself ?

@philips
Copy link
Contributor Author

philips commented Jul 30, 2018 via email

@tstromberg tstromberg added area/build-release kind/feature Categorizes issue or PR as related to a new feature. labels Sep 18, 2018
@tstromberg
Copy link
Contributor

I agree.

The only milestone that comes to mind for 1.0 is rock-solid stability. We could measure this in a lot of ways, such as <1% integration test flakiness, and/or that the top 5 errors that users encounter are directly actionable.

Either way, I think 1.0 would be a great Christmas or New Year's gift to minikube users.

@tstromberg tstromberg self-assigned this Oct 10, 2018
@afbjorklund
Copy link
Collaborator

I would probably have used 0.29.1 rather than 0.30 - but hey, it's only numbers...
It would be neat if the cri-o functionality could be restored before 1.0, though ?

@afbjorklund
Copy link
Collaborator

Added #3296 (for cri-o)

@tstromberg tstromberg removed their assignment Nov 6, 2018
@tstromberg tstromberg added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Jan 24, 2019
@tstromberg tstromberg self-assigned this Jan 24, 2019
@tstromberg tstromberg added this to the v1.0.0-candidate milestone Jan 24, 2019
@tstromberg tstromberg removed this from the v1.0.0 milestone Mar 20, 2019
@afbjorklund
Copy link
Collaborator

This is now closed, kubeadm is out of beta and cri-o works!

https://github.com/kubernetes/minikube/releases/tag/v1.0.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/build-release kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Development

No branches or pull requests

4 participants