Wrong kubeconfig is updated when installing 18.05 ce (Edge) and enabling Kubernetes

[janlund67]

• I have tried with the latest version of my channel (Stable or Edge)
• I have uploaded Diagnostics
• Diagnostics ID:

Expected Behavior

After installation it should be possible to switch to the context "docker-for-desktop-cluster" using kubectl config use-context docker-for-desktop-cluster

Actual behavior

error: no context exists with the name: "docker-for-desktop".

Information

• Windows Version: 10
• Docker for Windows Version: 18.05 CE Edge

If you have an existing kubeconfig that is not located at default location (C:\users{userid}\.kube\config) then your active kubeconfig is not updated, but a new kubekonfig is written to the default location.

It seems like the installation is not using the environment variable the tells the location of kubeconfig.

Workaround:
Open the config at the default location in a text editor.
Copy the contents to clipboard.
Open your current kubekonfig in a text editor
Paste the contents into the proper sections (clusters, contexts and users)

Steps to reproduce the behavior

1. Have an existing kubeconfig and kubectl installed.
2. Move the kubeconfig to some other folder.
3. Update your KUBECONFIG environment variable to reflect the change.
4. Test that you can still reach remote clusters.
5. Install 18.05 ce Egde, Enable Kubernetes and restart.
6. Run command kubectl config use-context docker-for-desktop-cluster

[docker-robott]

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

[docker-robott]

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