Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] gke-cluster create fails on subnet is not valid for Network #5

Open
dmizin opened this issue Jun 25, 2022 · 0 comments
Open

[BUG] gke-cluster create fails on subnet is not valid for Network #5

dmizin opened this issue Jun 25, 2022 · 0 comments
Labels
bug Something isn't working tracked

Comments

@dmizin
Copy link

dmizin commented Jun 25, 2022

Describe the bug
Running step "2-gke-cluster" produces error at network setup and fails

To Reproduce
Steps to reproduce the behavior:

  1. Go to multicloud-platform/gcp-gke/terraform/uswest1/2-gke-cluster/
  2. Run terraform apply
  3. See error
    │ Error: googleapi: Error 400: Subnetwork "projects/<edited>/regions/us-west2/subnetworks/environment01-us-west2-subnet" is not valid for Network "default"., badRequest │ │ with module.gke.google_container_cluster.primary, │ on ..\..\..\tfm\2-gke-cluster\main.tf line 7, in resource "google_container_cluster" "primary": │ 7: resource "google_container_cluster" "primary" { │

Expected behavior
GKE Cluster created

Additional context
Error appears to be the result of Line 12 of multicloud-platform/gcp-gke/tfm/2-gke-cluster/main.tf
Currently:
network = data.google_compute_network.vpc1.name
Should be:
network = "${var.network_name}"

Once updated, the cluster creation completes as expected. vpc1.name could point to expected name, or not - depending on customer's environment.

@dmizin dmizin added the bug Something isn't working label Jun 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working tracked
Projects
None yet
Development

No branches or pull requests

2 participants