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

Grammar + typos

Browse Source
This commit is contained in:
Brian Hoffmann
2021-06-16 11:14:36 +02:00
parent 9749287efd
commit 93a26a88cb
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -4,5 +4,5 @@ ring: trial
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/).
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.