Which command is used to execute an interactive shell inside a running container in a Kubernetes pod?

Which command is used to execute an interactive shell inside a running container in a Kubernetes pod?

• A. kubectl exec -it <pod_name> -c <container_name> --bash
• B. kubectl exec -c <container_name> --bash <pod_name>
• C. kubectl attach -it <pod_name> -c <container_name> --bash
• D. kubectl run -it <pod_name> --bash -c <container_name>

Answer: (A)

Running an interactive shell inside a running container is done with a command that uses a TTY and specifies both the pod and (if there are multiple containers) the target container, followed by the shell you want to run. The correct form does exactly that: it invokes the tool to execute a command inside the pod, allocates a terminal for interactivity, selects the specific container, and starts the bash shell inside it. This lets you interact with the container’s filesystem and processes in real time. Why this works better than the others: attaching to a container is about connecting to an already running process, not starting a new shell, so it isn’t suitable for initiating an interactive shell session. The other forms that rearrange arguments or use run try to either attach to the wrong thing or create a new pod instead of operating inside an existing one, which isn’t what you want when you need an interactive shell inside a running container.

Running an interactive shell inside a running container is done with a command that uses a TTY and specifies both the pod and (if there are multiple containers) the target container, followed by the shell you want to run. The correct form does exactly that: it invokes the tool to execute a command inside the pod, allocates a terminal for interactivity, selects the specific container, and starts the bash shell inside it. This lets you interact with the container’s filesystem and processes in real time.

Why this works better than the others: attaching to a container is about connecting to an already running process, not starting a new shell, so it isn’t suitable for initiating an interactive shell session. The other forms that rearrange arguments or use run try to either attach to the wrong thing or create a new pod instead of operating inside an existing one, which isn’t what you want when you need an interactive shell inside a running container.