In this day and age, code should be running well on all different kinds of platforms and environments. So let’s start debugging! Motivation (Why do we need remote debugging?)

All of this is done in the comfort of your own local machine’s VS Code. Instead of having to log variables and errors into the container log, there’s a great option of connecting to the Kubernetes cluster via SSH and then remote debugging the containerized deployed application from there, setting up breakpoints before and during the execution. Let’s say you have an application written in Typescript Node.js, and you want to put it in a Docker container and deploy it on a Kubernetes cluster on AWS, but you also still want to debug that application and develop it as you go. One of the most popular IDEs which offers that ability is VS Code. This makes the development process much smoother and try/fail cycles are much faster. In order to speed-up the development process, one of the must have features is the ability to conduct remote debugging. Today’s apps are usually deployed as Docker containers on remote machines and, as such, can be a bit challenging to develop and debug.

Visual studio code debug node