A DELETE_FAILED CloudFormation stack blocks eksctl create cluster
eksctl create cluster fails with AlreadyExistsException when a DELETE_FAILED CloudFormation stack lingers from a previous attempt. Manually delete the stack to unblock.
Today I Learned — Daily learnings
eksctl create cluster fails with AlreadyExistsException when a DELETE_FAILED CloudFormation stack lingers from a previous attempt. Manually delete the stack to unblock.
EKS Auto Mode (Karpenter) auto-terminates nodes with no pods via DisruptionTerminating: Empty. Expected cost-optimization behavior, not an error.
EKS Cluster Insights automatically checks kubelet version skew, add-on compatibility, and cluster health. Pair with kubent/pluto for a solid pre-upgrade checklist.
Upload source as tar.gz to S3, use --context=s3:// in a Kaniko Job, and it builds and pushes to ECR directly on EKS without a Docker daemon.
kubent runs both a Cluster collector and a Helm v3 collector that decodes release secrets. pluto's detect-all-in-cluster only covers live resources.
hostname spread alone can land all pods in the same AZ. Add topology.kubernetes.io/zone to guarantee cross-AZ distribution.
EKS auto-created VPC endpoints persist after cluster deletion, leaving ENIs in-use and blocking VPC deletion with DependencyViolation. Explicitly delete VPC endpoints and wait for ENI release.
AgentCore Runtime's ENI in the VPC may stay in-use for hours after agentcore destroy. Wait for it to become available before deleting the subnet and VPC.
kubectl delete application removes the CR but leaves Pods and Services running. Add resources-finalizer.argocd.argoproj.io for cascade deletion.
Identity Center looks global but lives in a specific region. Specifying the wrong idcRegion in EKS Capabilities triggers AccessDeniedException.