Kubernetes Event History and Upgrade Blocker Check for EKS Log in

Keep your EKS Kubernetes events for months, and find what will block your next node upgrade

Kubernetes deletes events after one hour. When a pod crash-looped at 3 AM or a node group upgrade failed with PodEvictionFailure, the evidence is usually gone by the time you look. Connect an AWS account with a narrow read-only role and an EKS access entry: we read the cluster's events every few minutes from outside the cluster, keep them for up to 90 days, and let you search, export and alert on them. Nothing is installed in your cluster.

Event history

Upgrade blocker check

  1. PodDisruptionBudget allows 0 disruptions
    Scale the workload above the budget (or fix its unhealthy pods), or change the budget to maxUnavailable: 1, then retry the upgrade.
  2. Single replica protected by a PodDisruptionBudget
    Run at least 2 replicas, or use maxUnavailable: 1 for this budget. With 1 replica the only pod can never be evicted.
  3. Pod tolerates every taint
    Give the toleration a key (for example only node.kubernetes.io/not-ready). Tolerating everything lets the pod land back on the node being drained.
  4. Pod without a controller
    Run it from a Deployment, StatefulSet or Job. A drain deletes a bare pod and nothing recreates it, so EKS stops unless you force the update.
  5. Node group update failed: PodEvictionFailure
    Fix the pods named here (usually their PodDisruptionBudget), then start the update again. Force update evicts them anyway, with downtime.
  6. Node group health issue
    Resolve the issue AWS reports for the node group before upgrading it.

Runs daily and on demand, and names the exact pods and PodDisruptionBudgets.

Read-only: the IAM role can only list and describe EKS clusters, node groups and updates. Inside the cluster it has the AWS-managed view policy (no Secrets). Limitation: clusters whose API endpoint is private only cannot be reached.

Try one cluster free for 14 days Log in