-
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
version: consider moving to 1.0 #2995
Comments
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. |
But even "kubeadm" is still in beta, so I am not sure that minikube is in a more stable state ? |
I don't think all components that minikube relies on need to be "1.0" for
this project to go 1.0.
In this particular case though: Beta in Kubernetes for kubeadm essentially
means that the project is ready to use but doesn't have final API stability
guarantees. And given the spin up / tear down method used by minikube I
don't think this is a concern.
…On Mon, Jul 30, 2018 at 6:26 AM Anders Björklund ***@***.***> wrote:
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 ?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#2995 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AACDCGGih5SbMVK_ah3bekUQUf1lQqZEks5uLwl0gaJpZM4VXK-a>
.
|
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. |
I would probably have used 0.29.1 rather than 0.30 - but hey, it's only numbers... |
Added #3296 (for cri-o) |
This is now closed, kubeadm is out of beta and cri-o works! |
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?
The text was updated successfully, but these errors were encountered: