Source: dzone.com
Whose Cluster Is It Anyway?Category: Business, Kubernetes, Docker, nginx, firewall
by Either developers decide they want to try something new, or the CTO does his research and decides to give it a try as it sounds promising.
In all cases, you need a way to triage all support cases and decide which team or a person is responsible for which part of the cluster management.
Such a solution would not be possible in most cases, as it requires a lot of experience from the development team to properly manage the cluster and make sure it is stable.
The responsibility split is done, so now we should only decide on the incident response scenarios, how do we triage issues, and figure out which team is responsible for fixing it (for example by monitoring cluster health and associating it with the failure), alerting and, of course, on-call schedules.
In all cases, you need a way to triage all support cases and decide which team or a person is responsible for which part of the cluster management.
Such a solution would not be possible in most cases, as it requires a lot of experience from the development team to properly manage the cluster and make sure it is stable.
The responsibility split is done, so now we should only decide on the incident response scenarios, how do we triage issues, and figure out which team is responsible for fixing it (for example by monitoring cluster health and associating it with the failure), alerting and, of course, on-call schedules.
Related Articles
Community Partners
DevOps Careers