gopaddle

While creating an EKS cluster, Cluster moves to Running state but the node pool is not created. 

Under Activity Logs, Event GETTING_EKS_CLUSTER_KUBEVERSION fails with timeout message as below:

In the Cloud Account section, Accessibility Check shows Failed status.

This happens when EKS Cluster takes too long to respond with its Kubernetes version. This may happen due to network delays or when EKS cluster is not in ready state. 

Click on Verfiy option to Accessibility Check. Once the Accessibility is verified, you can start creating a node pool under the Node Pool section.

Node Pool is not created while creating EKS Cluster, but the Cluster moves to running state. Event GETTING_EKS_CLUSTER_KUBEVERSION timesout.

Node Pool is not created while creating an EKS Cluster

Find answers and get help from Intercom Support and Community Experts

Empty Help Center

Uh oh. That page doesn’t exist.

Disappointed

Neutral

Smiley

Title

{assigneeName} needs more information from you