Skip to content

Kubernetes on call rotation

Tim Hockin edited this page Feb 2, 2015 · 2 revisions

Kubernetes "first responder" rotation

Kubernetes has generated a lot of public traffic: email, pull-requests, bugs, etc. So much traffic that it's becoming impossible to keep up with it all! This is a fantastic problem to have. In order to be sure that SOMEONE, but not EVERYONE on the team is paying attention to public traffic, we have instituted a "first responder" rotation.

Please read the notes on OSS collaboration, particularly the bits about hours. Specifically, each rotation is expected to be active primarily during work hours, less so off hours.

During regular workday work hours of your shift, your primary responsibility is to monitor the below-detailed traffic sources. You can check traffic in the evenings if you feel so inclined, but it is not expected to be as highly focused as work hours. For weekends, you should check traffic very occasionally (e.g. once or twice a day). Again, it is not expected to be as highly focused as workdays. It is assumed that over time, everyone will get weekday and weekend shifts, so the workload will balance out.

If you can not serve your shift, and you know this ahead of time, it is your responsibility to find someone to cover and to change the rotation. If you have an emergency, your responsibilities fall on the secondary rotation.

Traffic sources and responsibilities

If you are not on duty you DO NOT need to do these things. You are free to focus on "real work".

Frequently Asked Questions

How do I know whether someone has signed a CLA?

Check go/cla-signers.