This error occurs when Kubernetes encryption at rest fails due to KMS provider issues, typically when the external key management system is unavailable or misconfigured.
The "KMS provider error" indicates a problem with encryption/decryption when Kubernetes uses external Key Management Service (KMS) for encrypting data at rest.
kubectl get pods -n kube-system kube-apiserver-<node> -o yaml | grep -i kms
aws kms describe-key --key-id <arn>
kubectl logs -n kube-system pod/kube-apiserver-<node> | grep -i kms
aws sts get-caller-identity
KMS encryption: data encrypted in etcd with random DEK, DEK encrypted with KMS key.
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
kubectl get pods -n kube-system -w | grep kube-apiserver