1 Answer
- Newest
- Most votes
- Most comments
0
Based on the error message you provided, some potential causes for the failure could be:
- Insufficient IP addresses in the subnets associated with the EKS cluster. Check that there are enough available IPs.
- The subnets specified do not exist or are not tagged correctly. Verify the subnets exist and have the proper tags
- The security groups associated with the cluster do not exist. Check that the security groups exist.
- The elastic network interface limit for the AWS account has been reached. You may need to increase the limit.
- Insufficient permissions for the IAM role/user used to update the cluster. Verify the correct permissions are attached.
- The VPC associated with the cluster no longer exists. Check that the VPC still exists.
- Transient backend workflow issues. Try updating the cluster again after some time.
You can get more details on the specific error by describing the update failure with the AWS CLI:
aws eks describe-update --cluster-name my-cluster --update-id my-update-id
Relevant content
- asked 10 days ago
- asked a year ago
- AWS OFFICIALUpdated 3 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago