From dbe217dfc3b8d78fef7ff38aeab0cc161a2d597b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Daniel=20P=C3=B6tzinger?= Date: Fri, 18 Oct 2019 20:57:24 +0200 Subject: [PATCH] Historical split of Terraform and Helm --- radar/2018-03-01/helm-terraform.md | 14 -------------- radar/2018-03-01/helm.md | 8 ++++++++ radar/2018-03-01/terraform.md | 12 ++++++++++++ 3 files changed, 20 insertions(+), 14 deletions(-) delete mode 100644 radar/2018-03-01/helm-terraform.md create mode 100644 radar/2018-03-01/helm.md create mode 100644 radar/2018-03-01/terraform.md diff --git a/radar/2018-03-01/helm-terraform.md b/radar/2018-03-01/helm-terraform.md deleted file mode 100644 index 9f71e3b..0000000 --- a/radar/2018-03-01/helm-terraform.md +++ /dev/null @@ -1,14 +0,0 @@ ---- -title: "Helm/Terraform" -ring: trial -quadrant: tools - ---- - -For the infrastructure of our OM3 projects we run multiple Kubernetes clusters, and to orchestrate the infrastructure provisioning we quickly decided to go with Terraform. -Terraform allows us to easily manage our infrastructure, from AWS EC2 instances to RabbitMQ message queues. -Also, the Kops installer for Kubernetes on AWS uses Terraform as its main building brick, and we can trigger Kops via Terraform. - -For managing deployments within Kubernetes we use Helm, which makes templating Kubernetes configuration files super easy (also known as Helm charts). - -We bring both tools together to manage similar parts of the infrastructure, for example a shared file with domainname to application mappings allows us to provision Route 53 DNS entries via Terraform and then roll out Kubernetes Ingress definitions with the appropriate hostname to service mapping via Helm. diff --git a/radar/2018-03-01/helm.md b/radar/2018-03-01/helm.md new file mode 100644 index 0000000..8e25e28 --- /dev/null +++ b/radar/2018-03-01/helm.md @@ -0,0 +1,8 @@ +--- +title: "Helm" +ring: trial +quadrant: tools + +--- + +For managing deployments within Kubernetes we use Helm, which makes templating Kubernetes configuration files super easy (also known as Helm charts). diff --git a/radar/2018-03-01/terraform.md b/radar/2018-03-01/terraform.md new file mode 100644 index 0000000..167ca78 --- /dev/null +++ b/radar/2018-03-01/terraform.md @@ -0,0 +1,12 @@ +--- +title: "Terraform" +ring: trial +quadrant: tools + +--- + +For the infrastructure of our OM3 projects we run multiple Kubernetes clusters, and to orchestrate the infrastructure provisioning we quickly decided to go with Terraform. +Terraform allows us to easily manage our infrastructure, from AWS EC2 instances to RabbitMQ message queues. +Also, the Kops installer for Kubernetes on AWS uses Terraform as its main building brick, and we can trigger Kops via Terraform. + +We bring terraform together with [Helm](/tools/helm.html) to manage similar parts of the infrastructure, for example a shared file with domainname to application mappings allows us to provision Route 53 DNS entries via Terraform and then roll out Kubernetes Ingress definitions with the appropriate hostname to service mapping via Helm.