Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for worker pools on Google Cloud #148

Merged
merged 1 commit into from
Feb 27, 2018
Merged

Conversation

dghubble
Copy link
Member

@dghubble dghubble commented Feb 26, 2018

  • Allow "pools" of homogeneous workers to be created using the google-cloud/kubernetes/workers Terraform (sub)module
  • Examples: Add workers with a different machine type, larger disk, different preemptibility, GPUs (upcoming), etc.

Usage

Given a cluster "google-cloud-yavin" was created following the tutorial, worker pool(s) can be attached with:

module "yavin-worker-pool" {
  source = "git::https://github.com/poseidon/typhoon//google-cloud/container-linux/kubernetes/workers?ref=v1.9.4"

  # Google Cloud
  network      = "${module.google-cloud-yavin.network_name}"
  region       = "us-central1"
  count        = 2
  machine_type = "n1-standard-16"
  preemptible  = true

  cluster_name = "yavin-16x"
  ssh_authorized_key = "${var.ssh_authorized_key}"

  kubeconfig = "${module.google-cloud-yavin.kubeconfig}"
}

rel #127

* Set defaults for internal worker module's count,
machine_type, and os_image
* Allow "pools" of homogeneous workers to be created
using the google-cloud/kubernetes/workers module
@dghubble dghubble merged commit 160ae34 into master Feb 27, 2018
@dghubble dghubble deleted the gcp-worker-pools branch February 27, 2018 06:59
dghubble added a commit that referenced this pull request Mar 4, 2018
* 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
dghubble added a commit that referenced this pull request Mar 4, 2018
* 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
dghubble added a commit that referenced this pull request Mar 4, 2018
* 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant