CODEWITHSUNDEEP
google-kubernetes-engine
salman
salman

Reputation: 23

GKE Cluster Node not booting

I am trying to create a simple GKE cluster but the Nodes aren't booting properly due to this error: Failed to connect to storage.googleapis.com.

It's a private cluster and I have the NAT gateway for the network. The Node pool also uses the default compute service account which has access to everything.

Has anyone seen this error before or might know what the issue could be? Any help would be much appreciated, thank you very much :)!

Upvotes: 0

Views: 729

Answers (2)

Nani
Nani

Reputation: 853

Successful node registration to a GKE cluster depends on various factors, including the following:

  • Network connectivity.
  • Resource availability.
  • Service account permissions.

When GKE creates a node for your cluster, the initial step involves creating a new Compute Engine VM instance.

Instance creation might fail due to one of the following reasons:

Insufficient quota Resource availability Insufficient IP address space

In your situation, the error message suggests that the VM instance failed to download the necessary packages to prepare for running as a GKE node, possibly due to a connection timeout. This indicates that your cluster may not have fulfilled the networking requirements essential for connecting to Google APIs and services, such as storage.googleapis.com.

Depending on your network configuration, enabling this connection may involve configuring Private Google Access or setting up firewall rules and routes within your cluster's Virtual Private Cloud (VPC) network to permit the connection.

Upvotes: 0

Alex G
Alex G

Reputation: 1269

Thank you for the confirmation @salman, putting this as an answer to help others in the community.

The Failed to connect to storage.googleapis.com error is a common connection error on GKE Private Cluster that can be caused by wrong network configuration. Fixing this issue may include checking the firewall rules of your network or setting the configuration for the default-route.

For more information about this is issue you can check the following documentation and troubleshooting steps.

Upvotes: 2

Related Questions