Difference between revisions of "EKS troubleshooting"
Jump to navigation
Jump to search
Line 4: | Line 4: | ||
* [[EKS Pod Information Collector (EPIC)]] | * [[EKS Pod Information Collector (EPIC)]] | ||
− | curl -O https://raw.githubusercontent.com/awslabs/amazon-eks-ami/master/log-collector-script/linux/eks-log-collector.sh | + | [[curl -O]] https://raw.githubusercontent.com/awslabs/amazon-eks-ami/master/log-collector-script/linux/eks-log-collector.sh |
sudo bash eks-log-collector.sh | sudo bash eks-log-collector.sh | ||
+ | bash eks-pod-information-collector.sh --podname <pod_name> --namespace <pod_namespace> --service [service_name] | ||
== See also == | == See also == |
Revision as of 10:37, 26 February 2024
curl -O https://raw.githubusercontent.com/awslabs/amazon-eks-ami/master/log-collector-script/linux/eks-log-collector.sh sudo bash eks-log-collector.sh bash eks-pod-information-collector.sh --podname <pod_name> --namespace <pod_namespace> --service [service_name]
See also
- EKS troubleshooting, EKS log collector script, EKS Pod Information Collector (EPIC)
- 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: