|
| 1 | +<!-- BEGIN MUNGE: UNVERSIONED_WARNING --> |
| 2 | + |
| 3 | +<!-- BEGIN STRIP_FOR_RELEASE --> |
| 4 | + |
| 5 | +<img src="http://kubernetes.io/img/warning.png" alt="WARNING" |
| 6 | + width="25" height="25"> |
| 7 | +<img src="http://kubernetes.io/img/warning.png" alt="WARNING" |
| 8 | + width="25" height="25"> |
| 9 | +<img src="http://kubernetes.io/img/warning.png" alt="WARNING" |
| 10 | + width="25" height="25"> |
| 11 | +<img src="http://kubernetes.io/img/warning.png" alt="WARNING" |
| 12 | + width="25" height="25"> |
| 13 | +<img src="http://kubernetes.io/img/warning.png" alt="WARNING" |
| 14 | + width="25" height="25"> |
| 15 | + |
| 16 | +<h2>PLEASE NOTE: This document applies to the HEAD of the source tree</h2> |
| 17 | + |
| 18 | +If you are using a released version of Kubernetes, you should |
| 19 | +refer to the docs that go with that version. |
| 20 | + |
| 21 | +Documentation for other releases can be found at |
| 22 | +[releases.k8s.io](http://releases.k8s.io). |
| 23 | +</strong> |
| 24 | +-- |
| 25 | + |
| 26 | +<!-- END STRIP_FOR_RELEASE --> |
| 27 | + |
| 28 | +<!-- END MUNGE: UNVERSIONED_WARNING --> |
| 29 | +Kubernetes "Github and Build-cop" Rotation |
| 30 | +========================================== |
| 31 | + |
| 32 | +Preqrequisites |
| 33 | +-------------- |
| 34 | + |
| 35 | +* Ensure you have [write access to http://github.com/kubernetes/kubernetes](https://github.com/orgs/kubernetes/teams/kubernetes-maintainers) |
| 36 | + * Test your admin access by e.g. adding a label to an issue. |
| 37 | + |
| 38 | +Traffic sources and responsibilities |
| 39 | +------------------------------------ |
| 40 | + |
| 41 | +* GitHub [https://github.com/kubernetes/kubernetes/issues](https://github.com/kubernetes/kubernetes/issues) and [https://github.com/kubernetes/kubernetes/pulls](https://github.com/kubernetes/kubernetes/pulls): Your job is to be the first responder to all new issues and PRs. If you are not equipped to do this (which is fine!), it is your job to seek guidance! |
| 42 | + * Support issues should be closed and redirected to Stackoverflow (see example response below). |
| 43 | + * All incoming issues should be tagged with a team label (team/{api,ux,control-plane,node,cluster,csi,redhat,mesosphere,gke,release-infra,test-infra,none}); for issues that overlap teams, you can use multiple team labels |
| 44 | + * There is a related concept of "Github teams" which allow you to @ mention a set of people; feel free to @ mention a Github team if you wish, but this is not a substitute for adding a team/* label, which is required |
| 45 | + * [Google teams](https://github.com/orgs/kubernetes/teams?utf8=%E2%9C%93&query=goog-) |
| 46 | + * [Redhat teams](https://github.com/orgs/kubernetes/teams?utf8=%E2%9C%93&query=rh-) |
| 47 | + * [SIGs](https://github.com/orgs/kubernetes/teams?utf8=%E2%9C%93&query=sig-) |
| 48 | + * If the issue is reporting broken builds, broken e2e tests, or other obvious P0 issues, label the issue with priority/P0 and assign it to someone. This is the only situation in which you should add a priority/* label |
| 49 | + * non-P0 issues do not need a reviewer assigned initially |
| 50 | + * Assign any issues related to Vagrant to @derekwaynecarr (and @mention him in the issue) |
| 51 | + * All incoming PRs should be assigned a reviewer. |
| 52 | + * unless it is a WIP (Work in Progress), RFC (Request for Comments), or design proposal. |
| 53 | + * An auto-assigner [should do this for you] (https://github.com/kubernetes/kubernetes/pull/12365/files) |
| 54 | + * When in doubt, choose a TL or team maintainer of the most relevant team; they can delegate |
| 55 | + * Keep in mind that you can @ mention people in an issue/PR to bring it to their attention without assigning it to them. You can also @ mention github teams, such as @kubernetes/goog-ux or @kubernetes/kubectl |
| 56 | + * If you need help triaging an issue or PR, consult with (or assign it to) @brendandburns, @thockin, @bgrant0607, @quinton-hoole, @davidopp, @dchen1107, @lavalamp (all U.S. Pacific Time) or @fgrzadkowski (Central European Time). |
| 57 | + * At the beginning of your shift, please add team/* labels to any issues that have fallen through the cracks and don't have one. Likewise, be fair to the next person in rotation: try to ensure that every issue that gets filed while you are on duty is handled. The Github query to find issues with no team/* label is: [here](https://github.com/kubernetes/kubernetes/issues?utf8=%E2%9C%93&q=is%3Aopen+is%3Aissue+-label%3Ateam%2Fcontrol-plane+-label%3Ateam%2Fmesosphere+-label%3Ateam%2Fredhat+-label%3Ateam%2Frelease-infra+-label%3Ateam%2Fnone+-label%3Ateam%2Fnode+-label%3Ateam%2Fcluster+-label%3Ateam%2Fux+-label%3Ateam%2Fcsi+-label%3Ateam%2Fapi+-label%3Ateam%2Ftest-infra+). |
| 58 | + |
| 59 | +Example response for support issues: |
| 60 | + |
| 61 | + Please re-post your question to [stackoverflow](http://stackoverflow.com/questions/tagged/kubernetes). |
| 62 | + |
| 63 | + We are trying to consolidate the channels to which questions for help/support are posted so that we can improve our efficiency in responding to your requests, and to make it easier for you to find answers to frequently asked questions and how to address common use cases. |
| 64 | + |
| 65 | + We regularly see messages posted in multiple forums, with the full response thread only in one place or, worse, spread across multiple forums. Also, the large volume of support issues on github is making it difficult for us to use issues to identify real bugs. |
| 66 | + |
| 67 | + The Kubernetes team scans stackoverflow on a regular basis, and will try to ensure your questions don't go unanswered. |
| 68 | + |
| 69 | + Before posting a new question, please search stackoverflow for answers to similar questions, and also familiarize yourself with: |
| 70 | + * [the user guide](http://kubernetes.io/v1.0/) |
| 71 | + * [the troubleshooting guide](http://kubernetes.io/v1.0/docs/troubleshooting.html) |
| 72 | + |
| 73 | + Again, thanks for using Kubernetes. |
| 74 | + |
| 75 | + The Kubernetes Team |
| 76 | + |
| 77 | +Build-copping |
| 78 | +------------- |
| 79 | + |
| 80 | +* The [merge-bot submit queue](http://submit-queue.k8s.io/) ([source](https://github.com/kubernetes/contrib/tree/master/submit-queue)) should auto-merge all eligible PRs for you once they've passed all the relevant checks mentioned below and all [critical e2e tests] (https://goto.google.com/k8s-test/view/Critical%20Builds/) are passing. If the merge-bot been disabled for some reason, or tests are failing, you might need to do some manual merging to get things back on track. |
| 81 | +* Once a day or so, look at the [flaky test builds](https://goto.google.com/k8s-test/view/Flaky/); if they are timing out, clusters are failing to start, or tests are consistently failing (instead of just flaking), file an issue to get things back on track. |
| 82 | +* Jobs that are not in [critical e2e tests] (https://goto.google.com/k8s-test/view/Critical%20Builds/) or [flaky test builds](https://goto.google.com/k8s-test/view/Flaky/) are not your responsibility to monitor. The `Test owner:` in the job description will be automatically emailed if the job is failing. |
| 83 | +* If you are a weekday oncall, ensure that PRs confirming to the following pre-requisites are being merged at a reasonable rate: |
| 84 | + * [Have been LGTMd](https://github.com/kubernetes/kubernetes/labels/lgtm) |
| 85 | + * Pass Travis and Shippable. |
| 86 | + * Author has signed CLA if applicable. |
| 87 | +* If you are a weekend oncall, [never merge PRs manually](collab.md), instead add the label "lgtm" to the PRs once they have been LGTMd and passed Travis and Shippable; this will cause merge-bot to merge them automatically (or make them easy to find by the next oncall, who will merge them). |
| 88 | +* When the build is broken, roll back the PRs responsible ASAP |
| 89 | +* When E2E tests are unstable, a "merge freeze" may be instituted. During a merge freeze: |
| 90 | + * Oncall should slowly merge LGTMd changes throughout the day while monitoring E2E to ensure stability. |
| 91 | + * Ideally the E2E run should be green, but some tests are flaky and can fail randomly (not as a result of a particular change). |
| 92 | + * If a large number of tests fail, or tests that normally pass fail, that is an indication that one or more of the PR(s) in that build might be problematic (and should be reverted). |
| 93 | + * Use the Test Results Analyzer to see individual test history over time. |
| 94 | +* Flake mitigation |
| 95 | + * Tests that flake (fail a small percentage of the time) need an issue filed against them. Please read [this](https://github.com/kubernetes/kubernetes/blob/doc-flaky-test/docs/devel/flaky-tests.md#filing-issues-for-flaky-tests); the build cop is expected to file issues for any flaky tests they encounter. |
| 96 | + * It's reasonable to manually merge PRs that fix a flake or otherwise mitigate it. |
| 97 | + |
| 98 | +Contact information |
| 99 | +------------------- |
| 100 | + |
| 101 | +[@k8s-oncall](https://github.com/k8s-oncall) will reach the current person on call. |
| 102 | + |
| 103 | +<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> |
| 104 | +[]() |
| 105 | +<!-- END MUNGE: GENERATED_ANALYTICS --> |
0 commit comments