docs: tag blips with related academy trainings
This commit is contained in:
committed by
Stefan Rotsch
parent
e5738950cf
commit
291dfd138b
@@ -2,10 +2,9 @@
|
||||
title: "Terraform"
|
||||
ring: trial
|
||||
quadrant: tools
|
||||
tags: [academy training, devops]
|
||||
---
|
||||
|
||||
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 the infrastructure of our OM3 projects, we operate multiple Kubernetes clusters, and to orchestrate the infrastructure provisioning, we quickly decided to use Terraform. Terraform enables us to easily manage our infrastructure, from AWS EC2 instances to RabbitMQ message queues. Additionally, the Kops installer for Kubernetes on AWS utilizes Terraform as its main building block, and we can trigger Kops via Terraform.
|
||||
|
||||
We bring terraform together with [Helm](/platforms-and-aoe-services/helm/) to manage similar parts of the infrastructure, for example a shared file with domain name 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.
|
||||
We combine Terraform with [Helm](/platforms-and-aoe-services/helm/) to manage similar parts of the infrastructure. For example, a shared file with domain name to application mappings allows us to provision Route 53 DNS entries via Terraform and then deploy Kubernetes Ingress definitions with the appropriate hostname to service mapping via Helm.
|
||||
|
||||
Reference in New Issue
Block a user