This error occurs when encryption at rest is expected or attempted, but no KMS provider has been configured on the API server, leaving data unencrypted.
The "KMS provider not configured" error indicates that the API server is not configured with a KMS for encrypting data at rest.
kubectl get pods -n kube-system kube-apiserver-<node> -o yaml | grep encryption
sudo tee /etc/kubernetes/enc/provider.yaml
sudo vim /etc/kubernetes/manifests/kube-apiserver.yaml
sudo curl -o /usr/local/bin/k8s-kms ...
Configuration: provider order matters, caching includes cachesize and timeout, auto-reload enabled.
Failed to connect to server: connection refused (HTTP/2)
How to fix "HTTP/2 connection refused" error in Kubernetes
missing request for cpu in container
How to fix "missing request for cpu in container" in Kubernetes HPA
error: invalid configuration
How to fix "error: invalid configuration" in Kubernetes
kubectl create secret generic test --from-literal=key=value