# Debugging in Kubernetes

> For the complete documentation index, see [llms.txt](https://www.jetbrains.com/help/ruby/2026.3/llms.txt).

RubyMine supports the following Kubernetes debugging flows: on-the-fly pod troubleshooting with ephemeral containers and remote debugging with Telepresence, so you can diagnose various issues without leaving your IDE.

## Ephemeral containers

RubyMine supports attaching [ephemeral containers](https://kubernetes.io/docs/concepts/workloads/pods/ephemeral-containers/) to running pods without restarting them. This way, you can inspect a live Kubernetes environment, run diagnostic commands, and investigate issues directly inside a running pod.

An ephemeral container is temporarily added to an existing pod for debugging and runs alongside your application containers. For this purpose, RubyMine runs the `kubectl debug` command under the hood. You can either attach your custom debug container or use a lightweight BusyBox image, which provides common tools like `ping`, `netstat`, `wget`, and `top` out of the box.

For more details on debugging running pods, refer to the [Kubernetes
documentation](https://kubernetes.io/docs/tasks/debug/debug-application/debug-running-pod/).

Procedure: Attach BusyBox to a running pod

1. Open the [Services](services-tool-window.html) tool window: go to `View | Tool Windows | Services` or press `Alt+8` (Windows), `⌘ 8` (macOS), `⌘ 8` (IntelliJ IDEA Classic (macOS)), `⌘ 8` (macOS System Shortcuts), `Alt+8` (XWin), `Alt+8` (GNOME), `Alt+8` (KDE), `Alt+8` (Emacs), `Alt+8` (Sublime Text), `⌘ 8` (Sublime Text (macOS)), `Alt+8` (Visual Studio), `Alt+8` (Visual Studio (macOS)), `Meta+8` (TextMate), `Alt+8` (NetBeans), `Alt+8` (Eclipse), `⌘ 8` (Eclipse (macOS)).

2. Expand the node that lists running pods, right-click the pod you want to debug, and select `Ephemeral Debug Containers | Attach Busybox` from the context menu.

Alternatively, select the required pod, click ![the Ephemeral Container icon](https://resources.jetbrains.com/help/img/idea/2026.3/clouds-kubernetes.icons.newui.ephemeralStoppedContainer.png) on the toolbar, and select Attach Busybox from the dropdown.

![Attach BusyBox](https://resources.jetbrains.com/help/img/idea/2026.3/kubernetes_attach_busybox_container.png)

Procedure: Attach a custom container to a running pod

1. Open the [Services](services-tool-window.html) tool window: go to `View | Tool Windows | Services` or press `Alt+8` (Windows), `⌘ 8` (macOS), `⌘ 8` (IntelliJ IDEA Classic (macOS)), `⌘ 8` (macOS System Shortcuts), `Alt+8` (XWin), `Alt+8` (GNOME), `Alt+8` (KDE), `Alt+8` (Emacs), `Alt+8` (Sublime Text), `⌘ 8` (Sublime Text (macOS)), `Alt+8` (Visual Studio), `Alt+8` (Visual Studio (macOS)), `Meta+8` (TextMate), `Alt+8` (NetBeans), `Alt+8` (Eclipse), `⌘ 8` (Eclipse (macOS)).

2. Expand the node that lists running pods, right-click the pod you want to debug, and select `Ephemeral Debug Containers | Attach Custom` from the context menu.

Alternatively, select the required pod, click ![the Ephemeral Container icon](https://resources.jetbrains.com/help/img/idea/2026.3/clouds-kubernetes.icons.newui.ephemeralStoppedContainer.png) on the toolbar, and select Attach Custom from the dropdown.

3. In the Attach Custom Debug Container dialog, use the following fields to customize the `kubectl debug` command for starting and attaching an ephemeral container:

* Pod: select the pod you want to debug from the dropdown.

* Target: specify the target container inside the selected pod.

* Image: start typing the name of an image to use for debugging and then select it from the list of suggestions.

* Executable: specify an absolute path to the shell to run inside the ephemeral container after it starts (for example, `/bin/sh` for BusyBox or `/bin/bash` for Ubuntu).

* Options: provide additional configuration parameters for the debug container. For examples, refer to the [Kubernetes documentation](https://kubernetes.io/docs/reference/kubectl/generated/kubectl_debug/).

![the Attach Custom Debug Container dialog](https://resources.jetbrains.com/help/img/idea/2026.3/kubernetes_attach_custom_container.png)

> **Tip:**
> Hover over the ![the Preview Command](https://resources.jetbrains.com/help/img/idea/2026.3/clouds-kubernetes.icons.newui.consoleCommand.png) icon to preview the resulting `kubectl debug` command.

4. Click Attach to Pod.

When RubyMine starts a new ephemeral container and successfully attaches it to the pod, the Console tab opens, where you can run commands and inspect the pod.

![Debug console](https://resources.jetbrains.com/help/img/idea/2026.3/kubernetes_busybox_container_console.png)

If you [attach BusyBox](#attach-busybox-container-to-pod), RubyMine automatically uses `sh`. For [custom images](#attach-custom-container-to-pod), the IDE uses the shell specified in the Executable field.

The container is removed when you delete the pod it is attached to.

### Recent commands

When you attach an ephemeral container using the Ephemeral Debug Containers menu, RubyMine automatically saves the corresponding `kubectl debug` command. You can access and rerun it later from the Recent section.

![Recent commands](https://resources.jetbrains.com/help/img/idea/2026.3/kubernetes_recent_commands.png)

Procedure: Start an ephemeral container using a recent command

1. Open the [Services](services-tool-window.html) tool window: go to `View | Tool Windows | Services` or press `Alt+8` (Windows), `⌘ 8` (macOS), `⌘ 8` (IntelliJ IDEA Classic (macOS)), `⌘ 8` (macOS System Shortcuts), `Alt+8` (XWin), `Alt+8` (GNOME), `Alt+8` (KDE), `Alt+8` (Emacs), `Alt+8` (Sublime Text), `⌘ 8` (Sublime Text (macOS)), `Alt+8` (Visual Studio), `Alt+8` (Visual Studio (macOS)), `Meta+8` (TextMate), `Alt+8` (NetBeans), `Alt+8` (Eclipse), `⌘ 8` (Eclipse (macOS)).

2. Expand the node that lists running pods and right-click the pod you want to debug. Select Ephemeral Debug Containers and the required recent command from the context menu.

Alternatively, select the required pod, click ![the Ephemeral Container icon](https://resources.jetbrains.com/help/img/idea/2026.3/clouds-kubernetes.icons.newui.ephemeralStoppedContainer.png) on the toolbar, and select the recent command from the dropdown.

Procedure: Manage recent commands

1. Access recent commands:

* In the Settings dialog (`Ctrl+Alt+S` (Windows), `⌘ Comma` (macOS), `⌘ Comma` (IntelliJ IDEA Classic (macOS)), `⌘ Comma` (macOS System Shortcuts), `Ctrl+Alt+S` (XWin), `Ctrl+Alt+S` (GNOME), `Ctrl+Alt+S` (KDE), `Ctrl+Alt+S` (Emacs), `Ctrl+Alt+S` (Sublime Text), `⌘ Comma` (Sublime Text (macOS)), `Ctrl+Alt+S` (Visual Studio), `⌘ Comma` (Visual Studio (macOS)), `Meta+Comma` (TextMate), `Ctrl+Alt+S` (NetBeans), `Ctrl+Alt+S` (Eclipse), `⌘ Comma` (Eclipse (macOS))), select `Build, Execution, Deployment | Kubernetes | Cluster Interaction`.

* Open the Services tool window (`Alt+8` (Windows), `⌘ 8` (macOS), `⌘ 8` (IntelliJ IDEA Classic (macOS)), `⌘ 8` (macOS System Shortcuts), `Alt+8` (XWin), `Alt+8` (GNOME), `Alt+8` (KDE), `Alt+8` (Emacs), `Alt+8` (Sublime Text), `⌘ 8` (Sublime Text (macOS)), `Alt+8` (Visual Studio), `Alt+8` (Visual Studio (macOS)), `Meta+8` (TextMate), `Alt+8` (NetBeans), `Alt+8` (Eclipse), `⌘ 8` (Eclipse (macOS))). Right-click any running pod and select `Ephemeral Debug Containers | Edit Recents` from the context menu.

2. Navigate to the Ephemeral Debug Containers section.

* To add a new command that you can preconfigure and quickly start new ephemeral containers, click ![the Plus icon](https://resources.jetbrains.com/help/img/idea/2026.3/app-client.expui.general.add.svg). In the Add Debug Parameters dialog, you can specify an image, executable, and options for the `kubectl debug` command.

* To remove a command from recents, select it in the table and click ![the Minus icon](https://resources.jetbrains.com/help/img/idea/2026.3/app-client.expui.general.remove.svg).

* To edit an existing command, select it in the table and click ![the Edit icon](https://resources.jetbrains.com/help/img/idea/2026.3/app-client.expui.general.edit.svg). In the Add Debug Parameters dialog, change the image, executable, and options for the `kubectl debug` command.

## Telepresence

[Telepresence](https://telepresence.io/docs/quick-start) is a tool that lets you access services in a Kubernetes cluster, debug them, make, and test changes as if the services were running on your computer locally.

The Telepresence plugin works together with the Kubernetes plugin and allows you to:

* [Connect to Telepresence](#connect-to-telepresence) to access a service in the cluster by its DNS name.

* [Intercept a service](#intercept-traffic-from-cluster) to route traffic from the cluster to your local environment.

Procedure: Install the Telepresence plugin

This functionality relies on the [Telepresence](https://plugins.jetbrains.com/plugin/34535-telepresence)  plugin, which   you need to install and enable.

1. Press `Ctrl+Alt+S` (Windows), `⌘ Comma` (macOS), `⌘ Comma` (IntelliJ IDEA Classic (macOS)), `⌘ Comma` (macOS System Shortcuts), `Ctrl+Alt+S` (XWin), `Ctrl+Alt+S` (GNOME), `Ctrl+Alt+S` (KDE), `Ctrl+Alt+S` (Emacs), `Ctrl+Alt+S` (Sublime Text), `⌘ Comma` (Sublime Text (macOS)), `Ctrl+Alt+S` (Visual Studio), `⌘ Comma` (Visual Studio (macOS)), `Meta+Comma` (TextMate), `Ctrl+Alt+S` (NetBeans), `Ctrl+Alt+S` (Eclipse), `⌘ Comma` (Eclipse (macOS)) to open settings and then select `Plugins`.

2. Find the Telepresence plugin, and click Install. Restart the IDE if prompted.

Procedure: Connect to Telepresence

1. Open the [Services](services-tool-window.html) tool window: select `View | Tool Windows | Services` or press `Alt+8` (Windows), `⌘ 8` (macOS), `⌘ 8` (IntelliJ IDEA Classic (macOS)), `⌘ 8` (macOS System Shortcuts), `Alt+8` (XWin), `Alt+8` (GNOME), `Alt+8` (KDE), `Alt+8` (Emacs), `Alt+8` (Sublime Text), `⌘ 8` (Sublime Text (macOS)), `Alt+8` (Visual Studio), `Alt+8` (Visual Studio (macOS)), `Meta+8` (TextMate), `Alt+8` (NetBeans), `Alt+8` (Eclipse), `⌘ 8` (Eclipse (macOS)).

2. Right-click your Kubernetes cluster and select  Connect Telepresence. Alternatively, click ![Telepresence icon](https://resources.jetbrains.com/help/img/idea/2026.3/app-client.expui.actions.split.svg) in the toolbar. When prompted, enter your administrator account password required to start the Telepresence daemon. On Windows, allow `telepresence.exe` to be executed.

> **Tip:**
> On macOS and Linux, if Telepresence is not installed on your computer, a notification will appear, providing you with the option to install it. Telepresence will be installed in `/usr/local/bin`. Similarly, if [Traffic Manager](https://www.getambassador.io/docs/telepresence-oss/latest/install/manager) is not installed in the cluster, RubyMine will prompt you to install it.
>
>
>
> For Windows, follow the [Telepresence installation documentation](https://www.getambassador.io/docs/telepresence/latest/install?os=windows).

3. After installing Telepresence and Traffic Manager, click  Connect Telepresence  again.

You can now access services in the Kubernetes cluster by their DNS names as if the cluster were running on your workstation. For example, if you have an application that accepts requests to `hello-node:9001`, you can access it by its name.

Procedure: Intercept traffic from the cluster

Intercepts allow you to take traffic going to a service in the Kubernetes cluster and route it to the local service.

1. On the toolbar, click ![Telepresence icon](https://resources.jetbrains.com/help/img/idea/2026.3/app-client.expui.actions.split.svg) (Create New Interception) and then click Create new interception.

2. In the window that opens, in the Service list, select a workload to intercept. This can be a Deployment, a ReplicaSet, or a StatefulSet.

In the Ports field, specify the port on which the local instance of your service is running.

If the service is intercepted successfully, you can access it locally and use the IDE features to try, debug, and profile your application running in the cluster.

Procedure: Quit Telepresence

Telepresence interacts with one cluster at a time, so you may need to stop it before connecting to another cluster. Quitting Telepresence will stop all active intercepts.

1. Open the [Services](services-tool-window.html) tool window: select `View | Tool Windows | Services` or press `Alt+8` (Windows), `⌘ 8` (macOS), `⌘ 8` (IntelliJ IDEA Classic (macOS)), `⌘ 8` (macOS System Shortcuts), `Alt+8` (XWin), `Alt+8` (GNOME), `Alt+8` (KDE), `Alt+8` (Emacs), `Alt+8` (Sublime Text), `⌘ 8` (Sublime Text (macOS)), `Alt+8` (Visual Studio), `Alt+8` (Visual Studio (macOS)), `Meta+8` (TextMate), `Alt+8` (NetBeans), `Alt+8` (Eclipse), `⌘ 8` (Eclipse (macOS)).

2. Right-click your Kubernetes cluster and select Quit Telepresence. Alternatively, click ![Quit Telepresence icon](https://resources.jetbrains.com/help/img/idea/2026.3/app-client.expui.general.exit.svg) in the toolbar.

