Category: Kubernetes Provisioning Problems

Problems related to Kubernetes node provisioning and scaling, such as autoscaler failures, capacity issues, or provisioner configuration problems

ID	Title	Description	Category	Technology	Tags
prequel-2025-0090 High Impact: 8/10 Mitigation: 5/10	Karpenter version incompatible with Kubernetes version; Pods cannot be scheduled	Karpenter is unable to provision new nodes because the current Karpenter version is not compatible with Kubernetes version . This incompatibility causes validation errors in the nodeclass controller and prevents pods from being scheduled properly in the cluster.	Kubernetes Provisioning Problems	karpenter	AWS Karpenter Kubernetes
prequel-2025-0092 High Impact: 6/10 Mitigation: 4/10	AWS CNI intermittent runtime panics and failure to destroy pod network	This rule fires when the kubelet reports a series of `FailedKillPod / KillPodSandboxError` events that contain `rpc error: code = Unknown desc = failed to destroy network for sandbox…` together with a SIGSEGV / nil-pointer panic from `routed-eni-cni-plugin/cni.go` or `PluginMainFuncsWithError`. These messages indicate that the Amazon VPC CNI plugin crashed while tearing down a Pod’s network namespace, leaving the sandbox in an indeterminate state.	Kubernetes Provisioning Problems	aws-cni	EKS Pod Termination Network Panic