From 37d0f346aa2d2a5f639b199a15e4862de8dc7303 Mon Sep 17 00:00:00 2001 From: Fabrizio Branca Date: Fri, 30 Apr 2021 12:12:31 +0200 Subject: [PATCH] Update shared-responsibility.md --- radar/2021-01-01/shared-responsibility.md | 1 + 1 file changed, 1 insertion(+) diff --git a/radar/2021-01-01/shared-responsibility.md b/radar/2021-01-01/shared-responsibility.md index 34c970f..5dfd326 100644 --- a/radar/2021-01-01/shared-responsibility.md +++ b/radar/2021-01-01/shared-responsibility.md @@ -5,3 +5,4 @@ quadrant: methods-and-patterns --- Since introducing "Platform Engineering Team" the builds, maintains and operates our Kubernetes clusters and other releated platform services the question occurs who's in charge the various tasks like keeping things up and running, applying criticial security fixed, updated software in general, keeping an eye on the bill and many more topics. We're not proposing a solution on how to split responsibilities here, but we want to raise awareness for bringing everybody together and formally discuss all responsibilities and write them down similar to (and possible extending) AWS's [shared responsibilty modell](https://aws.amazon.com/compliance/shared-responsibility-model/). +Some of the topics include: 24/7 on-call support, broken deployment pipelines, and vulnerability scans.