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

Multiple worker pools #367

Closed
wants to merge 4 commits into from
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 25 additions & 0 deletions content/faq/how-to-implement-multiple-worker-pools.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,25 @@
---
title: "How can we implement multiple worker pools?"
description: "We use `kops` manifests (YAML) to define imperative Kubernetes architectures."
tags:
- kops
- Kubernetes
- manifest
- clusters
---

## Question

How can we implement multiple worker pools within our Kubernetes clusters?

## Answer

We use `kops` manifests (YAML) to define imperative Kubernetes architectures.

Inside the manifest (which looks like a standard Kubernetes resource) is a section for `kind: InstanceGroup` that allows for the definition of any number of node pools.

An example manifest is provided [here](https://github.com/cloudposse/geodesic/blob/master/rootfs/templates/kops/default.yaml).

An example of a project with the [Van Valen Research Lab at Caltech](https://github.com/vanvalenlab/kiosk/blob/master/conf/patches/gpu-nodes.yaml) demonstrates where a GPU node pool was added that is scaled down to zero by default.

Using the cluster autoscaler, when a pod is scheduled with the proper labels, the node pool is automatically scaled up.