docs: adopt service meshes (#310)
This commit is contained in:
committed by
Stefan Rotsch
parent
fd7a980345
commit
1de4e1fd01
14
radar/2024-06-01/service-mesh.md
Normal file
14
radar/2024-06-01/service-mesh.md
Normal file
@@ -0,0 +1,14 @@
|
|||||||
|
---
|
||||||
|
title: "Service Mesh"
|
||||||
|
ring: adopt
|
||||||
|
quadrant: platforms-and-aoe-services
|
||||||
|
tags: [architecture, devops, security]
|
||||||
|
---
|
||||||
|
|
||||||
|
Service Meshes are part of all our Kubernetes implementations now.
|
||||||
|
We value the additional security features they provide to our platforms.
|
||||||
|
|
||||||
|
We are using [Istio](https://istio.io/) on multiple production clusters
|
||||||
|
and are assessing [Cillium](https://docs.cilium.io/en/latest/network/servicemesh/)
|
||||||
|
as it also improves on Kubernetes' NetworkPolicies. We also consider [Linkerd](https://linkerd.io)
|
||||||
|
a good candidate when looking for a Service Mesh for your project.
|
||||||
Reference in New Issue
Block a user