|
1 | 1 | # Production Readiness Reviews
|
2 | 2 |
|
3 |
| -Production readiness reviews are intended to ensure that features merging into |
4 |
| -Kubernetes are observable, scalable and supportable, can be safely operated in |
5 |
| -production environments, and can be disabled or rolled back in the event they |
6 |
| -cause increased failures in production. |
| 3 | +Production readiness reviews (PRRs) are intended to ensure that enhancements |
| 4 | +merging into Kubernetes are observable, scalable and supportable, can be safely |
| 5 | +operated in production environments, and can be disabled or rolled back in the |
| 6 | +event they cause increased failures in production. |
7 | 7 |
|
8 |
| -Production readiness reviews are done by a separate team, apart from the SIG |
9 |
| -leads (although SIG lead approval is needed as well, of course). It is useful |
10 |
| -to have the viewpoint of a team that is not as familiar with the intimate |
11 |
| -details of the SIG, but is familiar with Kubernetes and with operating |
12 |
| -Kubernetes in production. Experience through our dry runs in 1.17-1.20 have |
13 |
| -shown that this slightly "outsider" view helps identify otherwise missed items. |
| 8 | +While approvals for an enhancement are still required from the respective SIG, |
| 9 | +production readiness reviews are done by the [Production Readiness subproject][prod-readiness] of SIG Architecture. |
| 10 | + |
| 11 | +It is useful to have the viewpoint of a team that is not as familiar with the |
| 12 | +intimate details of the SIG, but is familiar with Kubernetes and with operating |
| 13 | +Kubernetes in production. |
| 14 | + |
| 15 | +Experience through our dry runs in the Kubernetes 1.17 - 1.20 release cycles |
| 16 | +has shown that this slightly "outsider" view helps identify otherwise missed |
| 17 | +items. |
14 | 18 |
|
15 | 19 | Full documentation on the production readiness review process can be found on
|
16 | 20 | the SIG Architecture page [here][prod-readiness].
|
|
0 commit comments