mirror of
https://github.com/puppetmaster/typhoon.git
synced 2024-12-26 21:09:34 +01:00
45b556c08f
* Fix issue where worker firewall rules didn't apply to additional workers attached to a GCP cluster using the new "worker pools" feature (unreleased, #148). Solves host connection timeouts and pods not being scheduled to attached worker pools. * Add `name` field to GCP internal worker module to represent the unique name of of the worker pool * Use `cluster_name` field of GCP internal worker module for passing the name of the cluster to which workers should be attached
46 lines
1.3 KiB
HCL
46 lines
1.3 KiB
HCL
# Static IPv4 address for the Network Load Balancer
|
|
resource "google_compute_address" "ingress-ip" {
|
|
name = "${var.name}-ingress-ip"
|
|
}
|
|
|
|
# Network Load Balancer (i.e. forwarding rules)
|
|
resource "google_compute_forwarding_rule" "worker-http-lb" {
|
|
name = "${var.name}-worker-http-rule"
|
|
ip_address = "${google_compute_address.ingress-ip.address}"
|
|
port_range = "80"
|
|
target = "${google_compute_target_pool.workers.self_link}"
|
|
}
|
|
|
|
resource "google_compute_forwarding_rule" "worker-https-lb" {
|
|
name = "${var.name}-worker-https-rule"
|
|
ip_address = "${google_compute_address.ingress-ip.address}"
|
|
port_range = "443"
|
|
target = "${google_compute_target_pool.workers.self_link}"
|
|
}
|
|
|
|
# Network Load Balancer target pool of instances.
|
|
resource "google_compute_target_pool" "workers" {
|
|
name = "${var.name}-worker-pool"
|
|
|
|
health_checks = [
|
|
"${google_compute_http_health_check.ingress.name}",
|
|
]
|
|
|
|
session_affinity = "NONE"
|
|
}
|
|
|
|
# Ingress HTTP Health Check
|
|
resource "google_compute_http_health_check" "ingress" {
|
|
name = "${var.name}-ingress-health"
|
|
description = "Health check Ingress controller health host port"
|
|
|
|
timeout_sec = 5
|
|
check_interval_sec = 5
|
|
|
|
healthy_threshold = 2
|
|
unhealthy_threshold = 4
|
|
|
|
port = 10254
|
|
request_path = "/healthz"
|
|
}
|