This is a cache of https://docs.openshift.com/rosa/nodes/containers/nodes-containers-remote-commands.html. It is a snapshot of the page at 2024-11-25T03:20:49.766+0000.
Executing remote commands in a container - Working with containers | Nodes | Red Hat OpenShift <strong>service</strong> on AWS
    OpenShift docs are moving and will soon only be available at docs.redhat.com, the home of all Red Hat product documentation. Explore the new docs experience today.
  1. Documentation
    2. history bug_report picture_as_pdf
×

Executing remote commands in an Red Hat OpenShift service on AWS container

edit

You can use the CLI to execute remote commands in an Red Hat OpenShift service on AWS container.

edit

Executing remote commands in containers

Support for remote container command execution is built into the CLI.

Procedure

To run a command in a container:

$ oc exec <pod> [-c <container>] -- <command> [<arg_1> ... <arg_n>]

For example:

$ oc exec mypod date
Example output
Thu Apr  9 02:21:53 UTC 2015

For security purposes, the oc exec command does not work when accessing privileged containers except when the command is executed by a cluster-admin user.
edit

Protocol for initiating a remote command from a client

Clients initiate the execution of a remote command in a container by issuing a request to the Kubernetes API server:

/proxy/nodes/<node_name>/exec/<namespace>/<pod>/<container>?command=<command>

In the above URL:

  • <node_name> is the FQDN of the node.

  • <namespace> is the project of the target pod.

  • <pod> is the name of the target pod.

  • <container> is the name of the target container.

  • <command> is the desired command to be executed.

For example:

/proxy/nodes/node123.openshift.com/exec/myns/mypod/mycontainer?command=date

Additionally, the client can add parameters to the request to indicate if:

  • the client should send input to the remote container’s command (stdin).

  • the client’s terminal is a TTY.

  • the remote container’s command should send output from stdout to the client.

  • the remote container’s command should send output from stderr to the client.

After sending an exec request to the API server, the client upgrades the connection to one that supports multiplexed streams; the current implementation uses HTTP/2.

The client creates one stream each for stdin, stdout, and stderr. To distinguish among the streams, the client sets the streamType header on the stream to one of stdin, stdout, or stderr.

The client closes all streams, the upgraded connection, and the underlying connection when it is finished with the remote command execution request.