kubectl-logs - Man Page
Print the logs for a container in a pod
Examples (TL;DR)
- Show logs for a single-container pod:
kubectl logs pod_name
- Show logs for a specified container in a pod:
kubectl logs --container container_name pod_name
- Show logs for all containers in a pod:
kubectl logs --all-containers=true pod_name
- Stream pod logs:
kubectl logs --follow pod_name
- Show pod logs newer than a relative time like
10s
,5m
, or1h
:kubectl logs --since=relative_time pod_name
- Show the 10 most recent logs in a pod:
kubectl logs --tail=10 pod_name
- Show all pod logs for a given deployment:
kubectl logs deployment/deployment_name
Eric Paris Jan 2015
Synopsis
kubectl logs [Options]
Description
Print the logs for a container in a pod or specified resource. If the pod has only one container, the container name is optional.
Options
--all-containers=false Get all containers' logs in the pod(s).
-c, --container="" Print the logs of this container
-f, --follow=false Specify if the logs should be streamed.
--ignore-errors=false If watching / following pod logs, allow for any errors that occur to be non-fatal
--insecure-skip-tls-verify-backend=false Skip verifying the identity of the kubelet that logs are requested from. In theory, an attacker could provide invalid log content back. You might want to use this if your kubelet serving certificates have expired.
--limit-bytes=0 Maximum bytes of logs to return. Defaults to no limit.
--max-log-requests=5 Specify maximum number of concurrent logs to follow when using by a selector. Defaults to 5.
--pod-running-timeout=20s The length of time (like 5s, 2m, or 3h, higher than zero) to wait until at least one pod is running
--prefix=false Prefix each log line with the log source (pod name and container name)
-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, supports '=', '==', and '!='.(e.g. -l key1=value1,key2=value2). Matching objects must satisfy all of the specified label constraints.
--since=0s 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.
--since-time="" Only return logs after a specific date (RFC3339). Defaults to all logs. Only one of since-time / since may be used.
--tail=-1 Lines of recent log file to display. Defaults to -1 with no selector, showing all log lines otherwise 10, if a selector is provided.
--timestamps=false Include timestamps on each line in the log output
Options Inherited from Parent Commands
--as="" Username to impersonate for the operation. User could be a regular user or a service account in a namespace.
--as-group=[] Group to impersonate for the operation, this flag can be repeated to specify multiple groups.
--as-uid="" UID to impersonate for the operation.
--azure-container-registry-config="" Path to the file containing Azure container registry configuration information.
--cache-dir="/home/username/.kube/cache" Default cache directory
--certificate-authority="" Path to a cert file for the certificate authority
--client-certificate="" Path to a client certificate file for TLS
--client-key="" Path to a client key file for TLS
--cluster="" The name of the kubeconfig cluster to use
--context="" The name of the kubeconfig context to use
--disable-compression=false If true, opt-out of response compression for all requests to the server
--insecure-skip-tls-verify=false If true, the server's certificate will not be checked for validity. This will make your HTTPS connections insecure
--kubeconfig="" Path to the kubeconfig file to use for CLI requests.
--match-server-version=false Require server version to match client version
-n, --namespace="" If present, the namespace scope for this CLI request
--password="" Password for basic authentication to the API server
--profile="none" Name of profile to capture. One of (none|cpu|heap|goroutine|threadcreate|block|mutex)
--profile-output="profile.pprof" Name of the file to write the profile to
--request-timeout="0" 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
--tls-server-name="" Server name to use for server certificate validation. If it is not provided, the hostname used to contact the server is used
--token="" Bearer token for authentication to the API server
--user="" The name of the kubeconfig user to use
--username="" Username for basic authentication to the API server
--version=false --version, --version=raw prints version information and quits; --version=vX.Y.Z... sets the reported version
--warnings-as-errors=false Treat warnings received from the server as errors and exit with a non-zero exit code
Example
# Return snapshot logs from pod nginx with only one container kubectl logs nginx # Return snapshot logs from pod nginx with multi containers kubectl logs nginx --all-containers=true # Return snapshot logs from all containers in pods defined by label app=nginx kubectl logs -l app=nginx --all-containers=true # Return snapshot of previous terminated ruby container logs from pod web-1 kubectl logs -p -c ruby web-1 # Begin streaming the logs of the ruby container in pod web-1 kubectl logs -f -c ruby web-1 # Begin streaming the logs from all containers in pods defined by label app=nginx kubectl logs -f -l app=nginx --all-containers=true # Display only the most recent 20 lines of output in pod nginx kubectl logs --tail=20 nginx # Show all logs from pod nginx written in the last hour kubectl logs --since=1h nginx # Show logs from a kubelet with an expired serving certificate kubectl logs --insecure-skip-tls-verify-backend nginx # Return snapshot logs from first container of a job named hello kubectl logs job/hello # Return snapshot logs from container nginx-1 of a deployment named nginx kubectl logs deployment/nginx -c nginx-1
See Also
History
January 2015, Originally compiled by Eric Paris (eparis at redhat dot com) based on the kubernetes source material, but hopefully they have been automatically generated since!