From 1587b07e3ec371e30ea6d07fcb5714f4e640529e Mon Sep 17 00:00:00 2001 From: Nicki Washington Date: Sat, 19 Jan 2019 22:57:55 -0500 Subject: [PATCH 1/4] add implement multiple worker pools faq --- .../how-to-implement-multiple-worker-pools.md | 25 +++++++++++++++++++ 1 file changed, 25 insertions(+) create mode 100644 content/faq/how-to-implement-multiple-worker-pools.md diff --git a/content/faq/how-to-implement-multiple-worker-pools.md b/content/faq/how-to-implement-multiple-worker-pools.md new file mode 100644 index 000000000..042bc156e --- /dev/null +++ b/content/faq/how-to-implement-multiple-worker-pools.md @@ -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. From e1671f3b3c451f862bf8597a251aab2440aafe62 Mon Sep 17 00:00:00 2001 From: Nicki Washington Date: Sun, 20 Jan 2019 11:49:51 -0500 Subject: [PATCH 2/4] add does an IAP handle non-HTTP traffic to FAQ --- .../faq/does-an-IAP-handle-non-HTTP-traffic.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 content/faq/does-an-IAP-handle-non-HTTP-traffic.md diff --git a/content/faq/does-an-IAP-handle-non-HTTP-traffic.md b/content/faq/does-an-IAP-handle-non-HTTP-traffic.md new file mode 100644 index 000000000..5dcf41c80 --- /dev/null +++ b/content/faq/does-an-IAP-handle-non-HTTP-traffic.md @@ -0,0 +1,16 @@ +--- +title: "Does an IAP handle non-HTTP traffic?" +description: "IAP does not handle non-HTTP traffic because it’s designed to work with OAuth 2." +tags: +- Identity-Aware Proxy +- non-HTTP traffic +- OAuth 2 +--- + +## Question + +If we use an Identity-Aware Proxy (IAP), how does it handle non-HTTP traffic? + +## Answer + +IAP does not handle non-HTTP traffic because it’s designed to work with OAuth 2, which is strictly an HTTP-based authentication scheme. Non-HTTP traffic must flow over SSH tunnels or via a VPN (e.g. OpenVPN). From 69ba402fdc3063b50c22ddc686882e4a150bea7b Mon Sep 17 00:00:00 2001 From: Nicki Washington Date: Sun, 20 Jan 2019 12:56:37 -0500 Subject: [PATCH 3/4] add implement multiple worker pools faq --- content/faq/how-to-implement-multiple-worker-pools.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/faq/how-to-implement-multiple-worker-pools.md b/content/faq/how-to-implement-multiple-worker-pools.md index 042bc156e..f4b17cc9a 100644 --- a/content/faq/how-to-implement-multiple-worker-pools.md +++ b/content/faq/how-to-implement-multiple-worker-pools.md @@ -1,6 +1,6 @@ --- title: "How can we implement multiple worker pools?" -description: "We use kops manifests (YAML) to define imperative Kubernetes architectures." +description: "We use `kops` manifests (YAML) to define imperative Kubernetes architectures." tags: - kops - Kubernetes From 1830c070ffdaaf603fadc1eecad020ff9779cc4c Mon Sep 17 00:00:00 2001 From: drnickiw <45834465+drnickiw@users.noreply.github.com> Date: Sun, 20 Jan 2019 13:01:41 -0500 Subject: [PATCH 4/4] Remove file --- .../faq/does-an-IAP-handle-non-HTTP-traffic.md | 16 ---------------- 1 file changed, 16 deletions(-) delete mode 100644 content/faq/does-an-IAP-handle-non-HTTP-traffic.md diff --git a/content/faq/does-an-IAP-handle-non-HTTP-traffic.md b/content/faq/does-an-IAP-handle-non-HTTP-traffic.md deleted file mode 100644 index 5dcf41c80..000000000 --- a/content/faq/does-an-IAP-handle-non-HTTP-traffic.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: "Does an IAP handle non-HTTP traffic?" -description: "IAP does not handle non-HTTP traffic because it’s designed to work with OAuth 2." -tags: -- Identity-Aware Proxy -- non-HTTP traffic -- OAuth 2 ---- - -## Question - -If we use an Identity-Aware Proxy (IAP), how does it handle non-HTTP traffic? - -## Answer - -IAP does not handle non-HTTP traffic because it’s designed to work with OAuth 2, which is strictly an HTTP-based authentication scheme. Non-HTTP traffic must flow over SSH tunnels or via a VPN (e.g. OpenVPN).