diff --git a/daprdocs/content/en/developing-applications/debugging/bridge-to-kubernetes.md b/daprdocs/content/en/developing-applications/debugging/bridge-to-kubernetes.md index d4b953e37..b7c336628 100644 --- a/daprdocs/content/en/developing-applications/debugging/bridge-to-kubernetes.md +++ b/daprdocs/content/en/developing-applications/debugging/bridge-to-kubernetes.md @@ -1,14 +1,14 @@ --- type: docs title: "Bridge to Kubernetes support for Dapr services" -linkTitle: "Bridge to Kubernets" +linkTitle: "Bridge to Kubernetes" weight: 300 description: "Debug Dapr apps locally which still connected to your Kubernetes cluster" --- Bridge to Kubernetes allows you to run and debug code on your development computer, while still connected to your Kubernetes cluster with the rest of your application or services. This type of debugging is often called *local tunnel debugging*. -{{< button text="Learn more about Bridge to Kubernetes" link="https://code.visualstudio.com/docs/containers/bridge-to-kubernetes" >}} +{{< button text="Learn more about Bridge to Kubernetes" link="https://aka.ms/bridge-vscode-dapr" >}} ## Debug Dapr apps @@ -17,10 +17,10 @@ Bridge to Kubernetes supports debugging Dapr apps on your machine, while still h {{% alert title="Isolation mode" color="warning" %}} -[Isolation mode](https://code.visualstudio.com/docs/containers/bridge-to-kubernetes#_running-in-isolation-mode) is currently not supported with Dapr apps. Make sure to launch Bridge to Kubernetes mode without isolation. +[Isolation mode](https://aka.ms/bridge-isolation-vscode-dapr) is currently not supported with Dapr apps. Make sure to launch Bridge to Kubernetes mode without isolation. {{% /alert %}} ## Further reading - [Bridge to Kubernetes documentation](https://code.visualstudio.com/docs/containers/bridge-to-kubernetes) -- [VSCode integration]({{< ref vscode >}}) +- [VSCode integration]({{< ref vscode >}}) \ No newline at end of file