CadolesKube/typhoon
7
0
Fork 0
mirror of https://github.com/puppetmaster/typhoon.git synced 2025-07-17 03:01:35 +02:00
Code Issues Packages Projects Releases Wiki Activity

Add Google Cloud worker instances to a target pool

Browse Source 
* Background: A managed instance group of workers is used in backend
services for global load balancing (HTTP/HTTPS Ingress) and output
for custom global load balancing use cases
* Add worker instances to a target pool load balancing TCP/UDP
applications (NodePort or proxied). Output as `worker_target_pool`
* Health check for workers with a healthy Ingress controller. Forward
rules (regional) to target pools don't support different external and
internal ports so choosing nodes with Ingress allows proxying as a
workaround
* A target pool is a logical grouping only. It doesn't add costs to
clusters or worker pools
This commit is contained in:
Dalton Hubble
2019-03-30 15:12:55 -07:00
parent ae3a8a5770
commit aaa8e0261a
6 changed files with 60 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
google-cloud/container-linux/kubernetes/workers/workers.tf
View File

@ -1,4 +1,4 @@
# Regional managed instance group of workers
# Managed instance group of workers
resource "google_compute_region_instance_group_manager" "workers" {
name = "${var.name}-worker-group"
description = "Compute instance group of ${var.name} workers"
@ -8,7 +8,8 @@ resource "google_compute_region_instance_group_manager" "workers" {
instance_template = "${google_compute_instance_template.worker.self_link}"
region = "${var.region}"
target_size = "${var.count}"
target_size = "${var.count}"
target_pools = ["${google_compute_target_pool.workers.self_link}"]
named_port {
name = "http"