We should document that if running on Windows and connecting to a K8s cluster in WSL, you need to configure the security.allowedUNCHosts setting in VS Code to allow "\\wsl$".
Without this setting defined, the extension will fail to load with an ERR_UNC_HOST_NOT_ALLOWED error (currently hidden from the error message, but would be shown when #15 is fixed).
This only applies to the K8s VS Code extension which runs in a sandboxed environment. The K8s CLI plugin is not affected.
We should document that if running on Windows and connecting to a K8s cluster in WSL, you need to configure the
security.allowedUNCHostssetting in VS Code to allow "\\wsl$".Without this setting defined, the extension will fail to load with an
ERR_UNC_HOST_NOT_ALLOWEDerror (currently hidden from the error message, but would be shown when #15 is fixed).This only applies to the K8s VS Code extension which runs in a sandboxed environment. The K8s CLI plugin is not affected.