Kubectl logs

https://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#logs

• kubectl logs --help
• kubectl logs my-pod
• kubectl logs my-pod -c my-container
• kubectl logs --previous my-pod
• kubectl logs my-pod -f or kubectl logs my-pod --follow
• kubectl logs my-pod --tail=25
• kubectl logs my-pod -p or kubectl logs --previous

kubectl logs ${POD_NAME} ${CONTAINER_NAME}

Labels:

• kubectl logs -l app=elasticsearch
• kubectl logs your_container -c count

kubectl logs
error: expected 'logs [-f] [-p] (POD | TYPE/NAME) [-c CONTAINER]'.
POD or TYPE/NAME is a required argument for the logs command
See 'kubectl logs -h' for help and examples

Related

• kubectl exec
• CKA v1.23: Evaluate cluster and node logging
• CKA v1.18: Display scheduler events
• CKA v1.18: Manage cluster component logs
• CKA v1.18: Manage application logs
• CKA v1.15, CKA v1.21: Understand container logging
• stern -A .
• ktail
• kubectl top
• kubectl get events
• Sidecar container
• Kubernetes logging
• Fluent Bit
• Pixie

See also

• kubectl logs, ktail, stern, --previous, -c
• kubectl get: [ all | componentstatus | pods | apiservices | events | event| nodes | replicaset | services | svc | namespaces| hpa | secret | deployments | serviceaccounts | endpoints | daemonset | networkpolicy ], kubectl get -h
• K8s troubleshooting: kubectl logs, kubectl top, kubectl get events -A, kubectl describe pod, Liveness, Readiness, Kubernetes events, Pulling image, OOMKilled, ProbeWarning, Reason, FailedScheduling, errImagePull, ImagePullBackOff, Kubelet conditions: MemoryPressure, DiskPressure, KubeletHasSufficientPID, KubeletReady, kubectl [ debug | attach | exec ] kubectl cluster-info dump, SimKube, KWOK
• Kubectl information commands: cluster-info | view | pods | nodes | services | version | describe | logs