Skip to content

Commit

Permalink
Merge pull request #324 from sunilarjun/kube-config-WSL-behavior
Browse files Browse the repository at this point in the history
Update kubeconfig WSL Behavior
  • Loading branch information
sunilarjun authored Dec 6, 2023
2 parents 5ff2e74 + 0b261c3 commit 298a350
Showing 1 changed file with 12 additions and 0 deletions.
12 changes: 12 additions & 0 deletions docs/ui/preferences/wsl/integrations.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,3 +15,15 @@ With WSL, memory and CPU allocation is configured globally across all Linux dist

[WSL documentation]:
https://docs.microsoft.com/en-us/windows/wsl/wsl-config#options-for-wslconfig

:::caution warning: breaking change

:::

Starting with version `1.11.1`, Rancher Desktop no longer supports a symlink from the `~/.kube/config` file to the instance on your Windows filesystem. This is due to the Kubernetes endpoint differing between the Windows host and inside a WSL2 distribution. The application will replace found symlinks with a separate file instead.

If the file inside the distribution is a separate file, or a symlink to any other location, then Rancher Desktop will update that file with the `rancher-desktop` context.

However, if the file is a symlink to the default location on the host, then Rancher Desktop will delete it and create a new file with the cluster configuration that works from inside the distribution.

Consequently, the "Kubernetes context" menu entry for the notification will show (and change) the context for the Win32 side only. The contexts inside distributions will need to be managed manually from a command prompt.

0 comments on commit 298a350

Please sign in to comment.