oc logs [Options]
Print the logs for a resource
Supported resources are builds, build configs (bc), deployment configs (dc), and pods. When a pod is specified and has more than one container, the container name should be specified via -c. When a build config or deployment config is specified, you can view the logs for a particular version of it via --version.
If your pod is failing to start, you may need to use the --previous option to see the logs of the last attempt.
Get all containers's logs in the pod(s).
- -c, --container=""
Print the logs of this container
- -f, --follow=false
Specify if the logs should be streamed.
Maximum bytes of logs to return. Defaults to no limit.
The length of time (like 5s, 2m, or 3h, higher than zero) to wait until at least one pod is running
- -p, --previous=false
If true, print the logs for the previous instance of the container in a pod if it exists.
- -l, --selector=""
Selector (label query) to filter on.
Only return logs newer than a relative duration like 5s, 2m, or 3h. Defaults to all logs. Only one of since-time / since may be used.
Only return logs after a specific date (RFC3339). Defaults to all logs. Only one of since-time / since may be used.
Lines of recent log file to display. Defaults to -1 with no selector, showing all log lines otherwise 10, if a selector is provided.
Include timestamps on each line in the log output
Options Inherited from Parent Commands
Allow a SignatureVerifier to use keys which are technically non-compliant with RFC6962.
log to standard error as well as files
Max number of application metrics to store (per container)
Username to impersonate for the operation
Group to impersonate for the operation, this flag can be repeated to specify multiple groups.
Path to the file containing Azure container registry configuration information.
Comma-separated list of files to check for boot-id. Use the first one that exists.
Default HTTP cache directory
Path to a cert file for the certificate authority
Path to a client certificate file for TLS
Path to a client key file for TLS
CIDRs opened in GCE firewall for LB traffic proxy health checks
The name of the kubeconfig cluster to use
location of the container hints file
The name of the kubeconfig context to use
Indicates the tolerationSeconds of the toleration for notReady:NoExecute that is added by default to every pod that does not already have such a toleration.
Indicates the tolerationSeconds of the toleration for unreachable:NoExecute that is added by default to every pod that does not already have such a toleration.
use TLS to connect to docker
path to trusted CA
path to client certificate
path to private key
a comma-separated list of environment variable keys that needs to be collected for docker containers
Only report docker containers in addition to root stats
DEPRECATED: docker root is read from docker info (this is a fallback, default: /var/lib/docker)
Whether to enable cpu load reader
Max length of time for which to store events (per type). Value is a comma separated list of key values, where the keys are event types (e.g.: creation, oom) or "default" and the value is a duration. Default is applied to all non-specified event types
Max number of events to store (per type). Value is a comma separated list of key values, where the keys are event types (e.g.: creation, oom) or "default" and the value is an integer. Default is applied to all non-specified event types
Interval between global housekeepings
Interval between container housekeepings
If true, the server's certificate will not be checked for validity. This will make your HTTPS connections insecure
Path to the kubeconfig file to use for CLI requests.
Maximum number of seconds between log flushes
when logging hits line file:N, emit a stack trace
Whether to log the usage of the cAdvisor container
If non-empty, write log files in this directory
log to standard error instead of files
Comma-separated list of files to check for machine-id. Use the first one that exists.
Require server version to match client version
- -n, --namespace=""
If present, the namespace scope for this CLI request
The length of time to wait before giving up on a single server request. Non-zero values should contain a corresponding time unit (e.g. 1s, 2m, 3h). A value of zero means don't timeout requests.
- -s, --server=""
The address and port of the Kubernetes API server
logs at or above this threshold go to stderr
Writes in the storage driver will be buffered for this duration, and committed to the non memory backends as a single transaction
use secure connection with database
Bearer token for authentication to the API server
The name of the kubeconfig user to use
- -v, --v=0
log level for V logs
Print version information and quit
comma-separated list of pattern=N settings for file-filtered logging
# Start streaming the logs of the most recent build of the openldap build config. oc logs -f bc/openldap # Start streaming the logs of the latest deployment of the mysql deployment config. oc logs -f dc/mysql # Get the logs of the first deployment for the mysql deployment config. Note that logs # from older deployments may not exist either because the deployment was successful # or due to deployment pruning or manual deletion of the deployment. oc logs --version=1 dc/mysql # Return a snapshot of ruby-container logs from pod backend. oc logs backend -c ruby-container # Start streaming of ruby-container logs from pod backend. oc logs -f pod/backend -c ruby-container
June 2016, Ported from the Kubernetes man-doc generator