You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The google_container_cluster.primary resource gets created
This creates a default node pool, which immediately gets deleted (as configured by the safer-cluster module)
The node pool I configured now gets created (with the appropriate network tags)
My cluster is ready to go
Instead, however, this seems to be happening:
The google_container_cluster.primary resource gets created
The default node pool gets created and tries to register itself with the control plane
The default node pool cannot register itself with the control plane
The create operation finally times out and the cluster errors out with "Error waiting for creating GKE cluster: All cluster resources were brought up, but: only 0 nodes out of 1 have registered"
In my firewall logs, I can see that the default pool is trying to reach private.googleapis.com (i.e., DNS is working as expected). However, since I cannot add the allow-google-apis network tag to this pool, this egress gets denied:
This may be related to #305. Is there a way to add network tags to this pool so it can finish creating successfully (and get immediately deleted, haha)? Or is there an alternative recommended approach here?
The text was updated successfully, but these errors were encountered:
I'm trying to bring up a
safer-cluster
in a Shared VPC network roughly based on theterraform-example-foundation/3-networks
approach.In this VPC network, access to private Google APIs is configured with:
*.googleapis.com
toprivate.googleapis.com
(for resources without an external IP address, i.e., mysafer-cluster
nodes)allow-google-apis
Like in the
terraform-example-foundation-app
, I've added theallow-google-apis
network tag to thenode_pools_tags
variable.What I'd expect to happen is:
google_container_cluster.primary
resource gets createdsafer-cluster
module)Instead, however, this seems to be happening:
google_container_cluster.primary
resource gets createdcreate
operation finally times out and the cluster errors out with "Error waiting for creating GKE cluster: All cluster resources were brought up, but: only 0 nodes out of 1 have registered"In my firewall logs, I can see that the default pool is trying to reach private.googleapis.com (i.e., DNS is working as expected). However, since I cannot add the
allow-google-apis
network tag to this pool, this egress gets denied:This may be related to #305. Is there a way to add network tags to this pool so it can finish creating successfully (and get immediately deleted, haha)? Or is there an alternative recommended approach here?
The text was updated successfully, but these errors were encountered: