Debug Kubernetes applications with Cloud Code for IntelliJ Stay organized with collections Save and categorize content based on your preferences.

Java

Cloud Code automatically adds an environment variable, JAVA_TOOL_OPTIONS, with the appropriate JDWP configuration to enable debugging. If JAVA_TOOL_OPTIONS is already present, Cloud Code uses existing settings specified in JAVA_TOOL_OPTIONS.

Node.js

Depending on the structure of your application and its image build configuration, you might have to help the debugger map your local sources to the remote sources in the container. This enables the Node debugger to correctly process your breakpoints.

You can configure this in one of the following ways:

• Manual configuration

  Select the Develop on Kubernetes Run Configuration from the dropdown and then click Edit Configurations. On the Debug tab, configure the source mapping from your local application source to the source location in the remote container.

  [Choosing a source location in the source mapping section of the Debug tab]

  Configuration options:

  • File/directory - the local file or directory of your application running on Kubernetes.
  • Remote path - the path to the file or directory running in the container on Kubernetes.

• Automatic configuration

  You can choose to defer this mapping to Cloud Code. When you start your debug session, Cloud Code attempts to infer this mapping automatically. The inferred mapping is presented to you in a dialog; one dialog for each artifact you are debugging.

  [Remote path mapping dialog for each artifact specifying remote path being used]

  Configuration options:

  • Local path - the local path to the root of the artifact you are debugging.
  • Remote path - the path to the file or directory running in the container on Kubernetes. You can choose to override this with your own value. If you click Cancel, no mapping is applied.
  Note: Automatic mapping is a best effort guess based on heuristics.

Go

To configure your application for debugging, your app must be a Go Module-based application and be identified as being Go-based by setting one of the standard Go runtime environment variables in the container, such as GODEBUG, GOGC, GOMAXPROCS, or GOTRACEBACK. GOTRACEBACK=single is the default setting for Go and GOTRACEBACK=all is a generally useful configuration.

Optionally (but recommended), your app should be built with the -gcflags='all=-N -l' options to disable optimizations. Skaffold Profiles are a useful option for this purpose and can be set with the Deployment Profile field in your Run configuration on the Build/Deploy tab.

Python

To configure your application for debugging, ensure you meet the following prerequisites:

• IDE, edition, and plugin are compatible

  For compatible IDEs, editions, and plugins, see Supported IDEs.

• Skaffold version is 1.25.0 or greater

  You can allow Cloud Code to manage your dependencies, or point to a local Skaffold installation. See Preferences > Tools > Cloud Code > Dependencies.

• Python interpreter is configured

  Without a Python interpreter configured in your project, debugging won't work, as there is no way to run pydevd, the underlying Python debugger.

  IDE	How to configure
  IntelliJ IDEA	Python debugging with Cloud Code requires a Python SDK to be configured for your project. Go to File > Project Structure and add a Python SDK in the Project tab. If none exists, add one under the SDK tab.
  PyCharm	Go to File > Settings > Project > Python Interpreter or for Mac OS X, PyCharm > Preferences > Project > Python Interpreter, and add a Python interpreter.