From 1587b07e3ec371e30ea6d07fcb5714f4e640529e Mon Sep 17 00:00:00 2001 From: Nicki Washington Date: Sat, 19 Jan 2019 22:57:55 -0500 Subject: [PATCH 1/7] 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/7] 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 4b933e009f597b8f5696922adf07cbbd3375e351 Mon Sep 17 00:00:00 2001 From: Nicki Washington Date: Sun, 20 Jan 2019 13:23:25 -0500 Subject: [PATCH 3/7] remove does-an-IAP...md 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). From ce9553bac3960cecb154f00446bf95a84b25325b Mon Sep 17 00:00:00 2001 From: Nicki Washington Date: Sun, 20 Jan 2019 13:31:22 -0500 Subject: [PATCH 4/7] add faq-swap machine images --- content/faq/how-to-swap-machine-images.md | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) create mode 100644 content/faq/how-to-swap-machine-images.md diff --git a/content/faq/how-to-swap-machine-images.md b/content/faq/how-to-swap-machine-images.md new file mode 100644 index 000000000..7667ae5bc --- /dev/null +++ b/content/faq/how-to-swap-machine-images.md @@ -0,0 +1,20 @@ +--- +title: "How can we swap out machine images?" +description: "The base images are parameterized inside the kops manifest." +tags: +- kops +- images +- manifest +--- + +## Question + +How can we swap out machine images (e.g. tweak an AMI)? + +## Answer + +Inside the `kops` manifest, the base images are parameterized with an environment variable `KOPS_BASE_IMAGE`. + +An example is provided [here](https://github.com/cloudposse/geodesic/blob/master/rootfs/templates/kops/default.yaml#L150). + +More information is available [here](https://github.com/kubernetes/kops/blob/master/docs/images.md). From d4413f865be56330cc2292a1105d0f4e902f2940 Mon Sep 17 00:00:00 2001 From: Nicki Washington Date: Sun, 20 Jan 2019 13:41:23 -0500 Subject: [PATCH 5/7] remove how-to-swap-machine-images.md --- content/faq/how-to-swap-machine-images.md | 20 -------------------- 1 file changed, 20 deletions(-) delete mode 100644 content/faq/how-to-swap-machine-images.md diff --git a/content/faq/how-to-swap-machine-images.md b/content/faq/how-to-swap-machine-images.md deleted file mode 100644 index 7667ae5bc..000000000 --- a/content/faq/how-to-swap-machine-images.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -title: "How can we swap out machine images?" -description: "The base images are parameterized inside the kops manifest." -tags: -- kops -- images -- manifest ---- - -## Question - -How can we swap out machine images (e.g. tweak an AMI)? - -## Answer - -Inside the `kops` manifest, the base images are parameterized with an environment variable `KOPS_BASE_IMAGE`. - -An example is provided [here](https://github.com/cloudposse/geodesic/blob/master/rootfs/templates/kops/default.yaml#L150). - -More information is available [here](https://github.com/kubernetes/kops/blob/master/docs/images.md). From 2739fef8369403275abde7bdc3800924bb6d4818 Mon Sep 17 00:00:00 2001 From: Nicki Washington Date: Sun, 20 Jan 2019 14:46:04 -0500 Subject: [PATCH 6/7] add IAP-nonHTTP traffic FAQ --- .../faq/how-does-IAP-handle-non-HTTP-traffic.md | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) create mode 100644 content/faq/how-does-IAP-handle-non-HTTP-traffic.md diff --git a/content/faq/how-does-IAP-handle-non-HTTP-traffic.md b/content/faq/how-does-IAP-handle-non-HTTP-traffic.md new file mode 100644 index 000000000..d3d198cc6 --- /dev/null +++ b/content/faq/how-does-IAP-handle-non-HTTP-traffic.md @@ -0,0 +1,17 @@ +--- +title: "How does an Identity-Aware Proxy handle non-HTTP traffic?" +description: "It does not handle non-HTTP traffic because it’s designed to work with OAuth 2." +tags: +- Identity-Aware Proxy +- non-HTTP traffic +- OAuth 2 +- VPN +--- + +## 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 8fa6e4512594f85e18cc145ff01ae5012f3b7f1c Mon Sep 17 00:00:00 2001 From: Nicki Washington Date: Sun, 20 Jan 2019 22:21:47 -0500 Subject: [PATCH 7/7] remove multiple-worker-pools.md from IAP-nonHTTP --- .../how-to-implement-multiple-worker-pools.md | 25 ------------------- 1 file changed, 25 deletions(-) delete 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 deleted file mode 100644 index 042bc156e..000000000 --- a/content/faq/how-to-implement-multiple-worker-pools.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -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.