From 1de4e1fd0190f923ad1fedc60c3cf67336dbe67a Mon Sep 17 00:00:00 2001 From: Christian Zenker Date: Fri, 7 Jun 2024 12:50:47 +0200 Subject: [PATCH] docs: adopt service meshes (#310) --- radar/2024-06-01/service-mesh.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 radar/2024-06-01/service-mesh.md diff --git a/radar/2024-06-01/service-mesh.md b/radar/2024-06-01/service-mesh.md new file mode 100644 index 0000000..3167f8a --- /dev/null +++ b/radar/2024-06-01/service-mesh.md @@ -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.