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

Fix typos and change some grammatical constructions

Browse Source
This commit is contained in:
daniel.motzko
2021-07-02 13:54:18 +02:00
parent ea00db0ac6
commit 51c8a54795
54 changed files with 185 additions and 152 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
radar/2021-01-01/shared-responsibility.md
View File

@@ -2,7 +2,8 @@
title: "Shared Responsibility Model"
ring: trial
quadrant: methods-and-patterns
---
Since introducing "Platform Engineering Team" who build, maintain and operate our Kubernetes clusters and other related platform services, the question occurs who is in charge of the various tasks like keeping things up and running, applying critical security fixes, update 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 possibly extending) AWS's [shared responsibility model](https://aws.amazon.com/compliance/shared-responsibility-model/).
Some of the topics include: 24/7 on-call support, broken deployment pipelines, and vulnerability scans.
Since introducing "Platform Engineering Team" who build, maintain and operate our Kubernetes clusters and other related platform services, the question occurs who is in charge of the various tasks like keeping things up and running, applying critical security fixes, update 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 possibly extending) AWS's [shared responsibility model](https://aws.amazon.com/compliance/shared-responsibility-model/).
Some topics are 24/7 on-call support, broken deployment pipelines, and vulnerability scans.