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

Update embedded Kubernetes to 1.14 #3663

2 tasks done
dmaze opened this issue May 15, 2019 · 5 comments
2 tasks done

Update embedded Kubernetes to 1.14 #3663

dmaze opened this issue May 15, 2019 · 5 comments


Copy link

@dmaze dmaze commented May 15, 2019

  • I have tried with the latest version of my channel (Stable or Edge)
  • I have uploaded Diagnostics
  • Diagnostics ID: D9916B2F-B4F2-4269-8B4D-C01C0D3A537B/20190515152144

Expected behavior

If I click on (whale), Preferences, Reset, Reset Kubernetes cluster, then when the Kubernetes-in-Docker restarts, I am running a current version of Kubernetes, such as 1.14.

Actual behavior

I am running Kubernetes 1.10.11, which is rather out of date at this point.

$ kubectl version
Client Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.1", GitCommit:"b7394102d6ef778017f2ca4046abbaa23b88c290", GitTreeState:"clean", BuildDate:"2019-04-19T22:12:47Z", GoVersion:"go1.12.4", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.11", GitCommit:"637c7e288581ee40ab4ca210618a89a555b6e7e9", GitTreeState:"clean", BuildDate:"2018-11-26T14:25:46Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}


I've had Kubernetes support enabled for a while, though prodding around at low-level details suggests that objects are in fact getting deleted and recreated.

kubectl get pod -n kube-system kube-apiserver-docker-for-desktop -o jsonpath='{$}  {$.metadata.creationTimestamp}  {$.spec.containers[0].image}'
kube-apiserver-docker-for-desktop  2019-05-15T15:08:03Z

I've tried using the "Reset Kubernetes cluster" option. I have not tried the bigger hammers.

  • macOS Version: macOS Mojave Version 10.14.4

Diagnostic logs

Diagnose succeeded

Steps to reproduce the behavior

  1. (whale), Preferences, Kubernetes, Enable Kubernetes
  2. (whale), Preferences, Reset, "Reset Kubernetes cluster"
  3. kubectl version
Copy link

@EronWright EronWright commented May 26, 2019

Suggestions: add the 'area/kube' label and update the title to "Update Kubernetes to 1.1x".

Note that the Kubernetes versioning policy is -1/+1 between client and server; see Version Skew Policy.

Copy link

@alisondy alisondy commented May 28, 2019

running into this issue aswell, I also want to opt out of the prepackaged kubectl, as it's quite old, and conflicting with my dev env. Not sure if that should be covered under here or a separate issue

@dmaze dmaze changed the title Embedded Kubernetes is quite old Update embedded Kubernetes to 1.14 May 29, 2019
Copy link

@docker-desktop-robot docker-desktop-robot commented Aug 27, 2019

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30d of inactivity.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle stale

Copy link

@EronWright EronWright commented Oct 28, 2019

Note that Docker Desktop has been updated to Kubernetes 1.15.4 on Edge channel.

Copy link

@docker-desktop-robot docker-desktop-robot commented Jul 1, 2020

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle locked

@docker docker locked and limited conversation to collaborators Jul 1, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants