Historical split of Terraform and Helm

PaperCutSoftware · Oct 18, 2019 · dbe217d · dbe217d
1 parent 4b29bc5
commit dbe217d
Show file tree

Hide file tree

Showing 3 changed files with 20 additions and 14 deletions.
diff --git a/radar/2018-03-01/helm-terraform.md b/radar/2018-03-01/helm-terraform.md
diff --git a/radar/2018-03-01/helm.md 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
@@ -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.