{"id":86249,"date":"2021-06-02T09:00:16","date_gmt":"2021-06-02T16:00:16","guid":{"rendered":""},"modified":"2021-05-28T03:10:25","modified_gmt":"2021-05-28T10:10:25","slug":"enabling-local-tunnel-debugging-with-the-kubernetes-extension-for-vs-code","status":"publish","type":"post","link":"https:\/\/opensource.microsoft.com\/blog\/2021\/06\/02\/enabling-local-tunnel-debugging-with-the-kubernetes-extension-for-vs-code\/","title":{"rendered":"Enabling Local Tunnel Debugging with the Kubernetes extension for VS Code"},"content":{"rendered":"

Over the past several years, microservice architectures have become the norm when building cloud-native applications. What is often overlooked are the challenges developers face when working on a microservice-based app: by decoupling the app into multiple services, there are now more pieces to develop, debug, and manage. Debugging applications that depend on multiple services requires knowledge on how to configure, source, and run each microservice. Replicating the environment on your local machine becomes complex and, in some situations, not possible due to limited dev machine resources.<\/p>\n

The good news is, we have been working on a solution to help address these types of challenges.<\/p>\n

In partnership with developers from Red Hat, we are announcing the introduction of Local Tunnel Debugging for Kubernetes service in the Kubernetes extension for Visual Studio Code<\/a>, which enables you to use your native development tools against any cluster, live.<\/p>\n

With Local Tunnel Debugging, you can run\u00a0your\u00a0app\u2019s microservices natively on your development machine, using\u00a0the same\u00a0development tools\u00a0you have always used, while tunneling to a Kubernetes cluster where the rest of the application and the other services are running.\u00a0Requests\u00a0initiated\u00a0through the application will route between services running in the cluster until the service you are debugging is called. The request is then redirected to your development machine, to your locally running version. Local changes are executed, and the request is sent back into the cluster\u00a0seamlessly\u00a0to the other services.<\/p>\n

\"An<\/p>\n

\"A<\/p>\n

\"Multiple<\/p>\n

This form of development allows you to build and test your microservices in a more integrated way with the rest of the application and the other microservices. All of this happens in the local development environment, even before your code is committed to source control. The Local Tunnel Debug capability also sidesteps operational complexities, such as having to build Docker images and deploying to a cluster to see the changes.<\/p>\n

It also greatly simplifies microservice development by copying and applying the cluster\u2019s environment to the native service running on your workstation. This eliminates the need to manually source, configure, and compile external microservice dependencies during development. Environmental variables, connection strings, and volumes from the cluster environment are inherited and available to the microservice running locally.<\/p>\n

For development teams targeting a shared cluster, the local tunnel capability also offers a \u201cwork in isolation\u201d mode. As an isolated service is created, you also get a specific URL to ensure that only traffic using that URL is redirected to your local workstation. All other requests, using the original application URL, are redirected to the unmodified service running in the cluster, so your development environment does not cause disruption to your teammates.<\/p>\n

Whether you\u2019re connecting to your development cluster running in the cloud, or to your local cluster, the Local Tunnel Debug capability is available for your end-to-end debugging scenarios.<\/p>\n

Get started today<\/h2>\n

Learn how to use the Local Tunnel Debug capability by accessing our instructions<\/a>.<\/p>\n

Below is everything you need to get started with the Local Tunnel Debug capability.<\/p>\n