oc-logs man page
oc logs — Print the logs for a resource
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.
- -c, --container=""
Print the logs of this container
- -f, --follow=false
Specify if the logs should be streamed.
If true, include definitions of new APIs via calls to the API server. [default true]
If true, prompt the user for input when required.
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
View the logs of a particular build or deployment by version if greater than zero
Options Inherited from Parent Commands
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 container Azure container registry configuration information.
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
The name of the kubeconfig cluster to use
Path to the config file to use for CLI requests.
The name of the kubeconfig context to use
The Google Cloud Platform Service Account JSON Key to use for authentication.
If true, the server's certificate will not be checked for validity. This will make your HTTPS connections insecure
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.
The address and port of the Kubernetes API server
Bearer token for authentication to the API server
The name of the kubeconfig user to use
# 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