AJR/TechradarDev
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

docs: tag blips with related academy trainings

Browse Source
This commit is contained in:
Stefan Rotsch
2024-05-03 11:11:36 +02:00
committed by Stefan Rotsch
parent e5738950cf
commit 291dfd138b
11 changed files with 77 additions and 78 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
radar/2018-03-01/go-lang.md
View File

@@ -2,7 +2,10 @@
title: "Go / Golang"
ring: trial
quadrant: languages-and-frameworks
tags: [academy training, coding]
---
We have moved Go to Trial because multiple teams have used Go with success for different services and tools.
The learning curve and productivity have proven to be immense and we are convinced that this language will find more adoption in other teams.
We have decided to trial Go because multiple teams have successfully used it for various services and tools.
The learning curve and productivity have proven to be significant, and we are convinced that this language will gain
more adoption in other teams.

15
radar/2018-03-01/kubernetes.md
View File

@@ -2,12 +2,13 @@
title: "Kubernetes"
ring: adopt
quadrant: platforms-and-aoe-services
tags: [devops]
tags: [academy training, devops]
---
Kubernetes has developed into the quasi-standard for container orchestration: Nearly every cloud provider provides managed Kubernetes, and even Docker Enterprise uses Kubernetes.
We are running several production systems with Kubernetes and we are using it in concepts such as:
* "secrets" and "configmaps" to manage configurations for the applications. By updating these resources with an automated configuration pipeline you have a great method for configuration management.
* Autoscaling of Kubernetes nodes and the usage of "horizontal pod scaling" inside Kubernetes allows elastic scaling
* The support of managing permissions with OAuth allows you to secure Kubernetes with [Keycloak](/tools/keycloak/) (SSO)
* Kubernetes extensibility and API can be used for automation and customization. There is a growing ecosystem around extensions, which adds additional features.
Kubernetes has evolved into the quasi-standard for container orchestration: Nearly every cloud provider offers managed Kubernetes, and even Docker Enterprise utilizes Kubernetes.
We run several production systems with Kubernetes and employ it in concepts such as:
- Utilizing "secrets" and "configmaps" to manage configurations for applications. By updating these resources with an automated configuration pipeline, you have an excellent method for configuration management.
- Implementing autoscaling of Kubernetes nodes and utilizing "horizontal pod scaling" within Kubernetes allows for elastic scaling.
- Leveraging support for managing permissions with OAuth, enabling you to secure Kubernetes with [Keycloak](/tools/keycloak/) (SSO).
- Utilizing Kubernetes' extensibility and API for automation and customization. There is a growing ecosystem around extensions, which adds additional features.

7
radar/2018-03-01/terraform.md
View File

@@ -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.