-
Notifications
You must be signed in to change notification settings - Fork 5k
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
Warn if incompatible kubectl version is in use #3329
Comments
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
If someone wants to implement this:
|
Assigning this ticket to myself |
/assign @nanikjava |
@nanikjava - excellent news! Please let me know if you need any additional help, either here or on the Slack #minikube channel. |
Output from 'kubectl version --output=json' is applicable for all version of kubectl. Following is a sample output
|
Fixes: kubernetes#3329 Modification is done inside start.go where additional checking on the version returned via the kubectl CLI is checked. Running 'kubectl version --output=json' will return both client and server information.
@tstromberg PR ready #5596 Thank you. |
Currently, it's possible to use minikube on a host running v1.6.1 against a master running v1.12.1. This isn't a supported configuration, as per https://github.com/kubernetes/community/blob/master/contributors/design-proposals/release/versioning.md#supported-releases-and-component-skew
We should have a flight check that validates that ancient version of kubectl aren't in use. This would also serve as an early warning to users about issues such as #3203
The text was updated successfully, but these errors were encountered: