karmadactl exec
Execute a command in a container in a cluster
Synopsis
Execute a command in a container in a cluster.
karmadactl exec (POD | TYPE/NAME) [-c CONTAINER] (-C CLUSTER) -- COMMAND [args...]
Examples
# Get output from running the 'date' command from pod mypod, using the first container by default in cluster(member1)
karmadactl exec mypod -C=member1 -- date
# Get output from running the 'date' command in ruby-container from pod mypod in cluster(member1)
karmadactl exec mypod -c ruby-container -C=member1 -- date
# Get output from running the 'date' command in ruby-container from pod mypod in cluster(member1)
karmadactlexec mypod -c ruby-container -C=member1 -- date
# Switch to raw terminal mode; sends stdin to 'bash' in ruby-container from pod mypod in cluster(member1)
# and sends stdout/stderr from 'bash' back to the client
karmadactl exec mypod -c ruby-container -C=member1 -i -t -- bash -il
# Get output from running 'date' command from the first pod of the deployment mydeployment, using the first container by default in cluster(member1)
karmadactl exec deploy/mydeployment -C=member1 -- date
# Get output from running 'date' command from the first pod of the service myservice, using the first container by default in cluster(member1)
karmadactl exec svc/myservice -C=member1 -- date
Options
-C, --cluster string Specify a member cluster
-c, --container string Container name. If omitted, use the kubectl.kubernetes.io/default-container annotation for selecting the container to be attached or the first container in the pod will be chosen
-f, --filename strings to use to exec into the resource
-h, --help help for exec
--karmada-context string The name of the kubeconfig context to use
-n, --namespace string If present, the namespace scope for this CLI request
--pod-running-timeout duration The length of time (like 5s, 2m, or 3h, higher than zero) to wait until at least one pod is running (default 1m0s)
-q, --quiet Only print output from the remote session
-i, --stdin Pass stdin to the container
-t, --tty Stdin is a TTY
Options inherited from parent commands
--add-dir-header If true, adds the file directory to the header of the log messages
--alsologtostderr log to standard error as well as files (no effect when -logtostderr=true)
--kubeconfig string Paths to a kubeconfig. Only required if out-of-cluster.
--log-backtrace-at traceLocation when logging hits line file:N, emit a stack trace (default :0)
--log-dir string If non-empty, write log files in this directory (no effect when -logtostderr=true)
--log-file string If non-empty, use this log file (no effect when -logtostderr=true)
--log-file-max-size uint Defines the maximum size a log file can grow to (no effect when -logtostderr=true). Unit is megabytes. If the value is 0, the maximum file size is unlimited. (default 1800)
--logtostderr log to standard error instead of files (default true)
--one-output If true, only write logs to their native severity level (vs also writing to each lower severity level; no effect when -logtostderr=true)
--skip-headers If true, avoid header prefixes in the log messages
--skip-log-headers If true, avoid headers when opening log files (no effect when -logtostderr=true)
--stderrthreshold severity logs at or above this threshold go to stderr when writing to files and stderr (no effect when -logtostderr=true or -alsologtostderr=false) (default 2)
-v, --v Level number for the log level verbosity
--vmodule moduleSpec comma-separated list of pattern=N settings for file-filtered logging
SEE ALSO
- karmadactl - karmadactl controls a Kubernetes Cluster Federation.