etcd database full with Kubernetes events. Fix by cleaning up old events, increasing quota, or using separate etcd for events.
Kubernetes events can consume most of etcd storage, causing the cluster to reach quota and rejecting new writes.
kubectl exec -n kube-system etcd-<node> -- etcdctl endpoint statuskubectl delete events --all -AAdd --quota-backend-bytes flag to etcd.
Set --event-ttl=1h on API server.
Consider dedicated etcd instance for events.
Failed to connect to server: connection refused (HTTP/2)
How to fix "HTTP/2 connection refused" error in Kubernetes
No subnets found for EKS cluster
How to fix "eks subnet not found" in Kubernetes
missing request for cpu in container
How to fix "missing request for cpu in container" in Kubernetes HPA
Track metrics and set alerts.