E M 6bc28b68d7
change monitoring to default service
Cluster deployment seems to be stalling because the metrics service is not started. So returning it to default to see if that fixes the issue.
2026-04-28 17:50:43 +10:00

54 lines
1.3 KiB
HCL

# Both node pools are inline so GCP provisions them in parallel during
# cluster creation, avoiding the sequential create penalty of a separate
# google_container_node_pool resource.
resource "google_container_cluster" "this" {
name = local.name
location = var.zone
project = var.project
deletion_protection = false
# Send pod stdout/stderr to Cloud Logging automatically
logging_service = "logging.googleapis.com/kubernetes"
monitoring_service = "monitoring.googleapis.com/kubernetes"
node_pool {
name = var.node_pool_name
initial_node_count = var.node_pool_min
autoscaling {
min_node_count = var.node_pool_min
max_node_count = var.node_pool_max
}
node_config {
machine_type = var.node_pool_machine_type
labels = var.node_pool_labels
oauth_scopes = [
"https://www.googleapis.com/auth/cloud-platform",
]
}
}
node_pool {
name = var.tests_pool_name
initial_node_count = 0
autoscaling {
min_node_count = 0
max_node_count = var.tests_pool_max
}
node_config {
machine_type = var.tests_pool_machine_type
spot = true
labels = var.tests_pool_labels
oauth_scopes = [
"https://www.googleapis.com/auth/cloud-platform",
]
}
}
}