Event-exporter-gke in kube-system namespace crashes when deploying GKE with Terraform

Terraform Providers
1

I have deployed a GKE cluster version 1.16.10-gke.8 and get the following error in the event-exporter-gke pods:

 F0709 14:22:50.443097       1 main.go:123] Failed to get GCE config: error while getting instance (node) name: metadata: GCE metadata "instance/name" not defined                                                                                                                                                                                                                          
stream closed

Can someone please help me to figure out if this is a bug or my setup is broken?

Terraform 0.12.24, terraform_google_provider 3.29.0.

resource "google_container_cluster" "kube" {
  provider = google-beta

  name               = local.clusterName
  initial_node_count = "1"
  min_master_version = "1.16"

  master_auth {
    username = local.username
    password = random_string.password.result
  }

  lifecycle {
    ignore_changes = [
      min_master_version,
      initial_node_count,
    ]
  }

  node_config {
    machine_type = var.NodeMachineType

    oauth_scopes = [
      "https://www.googleapis.com/auth/compute",
      "https://www.googleapis.com/auth/devstorage.read_only",
      "https://www.googleapis.com/auth/logging.write",
      "https://www.googleapis.com/auth/monitoring",
    ]

    tags = [
      local.nodeTag,
    ]
  }

  resource_labels = {
    "do_not_remove" = "true"
  }

  vertical_pod_autoscaling {
    enabled = true
  }

  addons_config {
    horizontal_pod_autoscaling {
      disabled = true
    }
  }

  master_authorized_networks_config {
    dynamic "cidr_blocks" {
      for_each = merge(local.whitelistExternalIps, local.whitelistInternalIps)
      iterator = ip

      content {
        cidr_block   = ip.value
        display_name = ip.key
      }
    }
  }

  workload_identity_config {
    identity_namespace = "${var.project}.svc.id.goog"
  }
}
2

I have the same error running a GKE cluster.

3

Same here for several clusters

4

FWIW, I just upgraded to 1.16.10-gke.8 through the GKE UI and I get the same thing.

5

Same thing in v1.16.8-gke.15

6

The issue seems to be resolved now. Probably was some hiccup on Google’s side.