Cluster-level problems
Things broke after a cluster upgrade
Most often: manifests or Helm charts using removed API versions (e.g. policy/v1beta1 PodDisruptionBudget, autoscaling/v2beta2 HPA, old flowcontrol APIs). Apply fails with no matches for kind ... in version .... Check before upgrading with kubent/pluto, EKS upgrade insights, and API server deprecated-API metrics; update manifests and chart versions. Also add-on version compatibility (CNI, CoreDNS, kube-proxy, controllers).
Namespace stuck in Terminating
Resources inside still have finalizers whose controller is gone (an uninstalled operator/CRD, a load balancer controller removed before its Ingresses):
kubectl get namespace shop -o json | jq '.status.conditions'
kubectl api-resources --verbs=list --namespaced -o name | xargs -n1 kubectl get -n shop --ignore-not-found --show-kind
Fix the controller (reinstall it so it can clean up) or, as a last resort and knowing the external resources may be orphaned, remove the finalizers from the stuck objects.
Admission webhooks blocking everything
Errors like failed calling webhook "validation.gatekeeper.sh": ... context deadline exceeded — a webhook with failurePolicy: Fail is down or slow. Deploys fail cluster-wide. Fix the webhook's pods; if they can't start because the webhook blocks them, temporarily exclude system namespaces or edit the webhook configuration. Prevent with HA webhooks, short timeouts and namespace exemptions.
RBAC "forbidden"
Error from server (Forbidden): pods is forbidden: User "system:serviceaccount:shop:orders" cannot list resource "pods" ... — grant the needed verbs via Role/RoleBinding (least privilege). Test with kubectl auth can-i. On EKS, human access problems are usually access entries (or aws-auth on older clusters).
Certificates and control plane
Self-managed clusters: expired component certificates (kubeadm defaults to 1 year) → API server refusing connections; etcd disk latency → slow API; check kubectl get --raw /readyz?verbose. On EKS the control plane is managed — look at control plane logs in CloudWatch and AWS Health events.