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 |
||
|---|---|---|
| .. | ||
| cl | ||
| ingress.tf | ||
| outputs.tf | ||
| variables.tf | ||
| workers.tf | ||