1 Answer
- Newest
- Most votes
- Most comments
0
I think it means that the EKS cluster can't perform all of its functions, such as creating new Kubernetes secrets and running pods. You can't create a new Kubernetes secret and encrypt it, and the pods running inside the cluster can't decrypt the Kubernetes secrets as the existing KMS key is deleted.
So, you would have to create a new EKS cluster with a new KMS key.
answered a year ago
Relevant content
- asked 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 8 months ago