Difference between revisions of "Crictl logs"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
{{lc}} | {{lc}} | ||
| + | |||
| + | crictl logs 27b6a18c0f89c | ||
| + | ... | ||
| + | I0913 12:53:03.096620 1 server_others.go:212] Using [[iptables Proxier]]. | ||
| + | ... | ||
Revision as of 10:35, 3 December 2022
crictl logs 27b6a18c0f89c ... I0913 12:53:03.096620 1 server_others.go:212] Using iptables Proxier. ...
kubectl logs ktail crictl ps
See also
crictl [ logs | ps | pods | exec | config | images ], /etc/crictl.yaml, crictl --help, Kubelet Container Runtime Interface (CRI)- 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
Advertising:
