@@ -9,7 +9,7 @@ Production readiness reviews are done by a separate team, apart from the SIG
9
9
leads (although SIG lead approval is needed as well, of course). It is useful to
10
10
have the viewpoint of a team that is not as familiar with the intimate details
11
11
of the SIG, but * is* familiar with Kubernetes and with operating Kubernetes in
12
- production. Experience through our dry runs in 1.19 and 1.20 have shown that
12
+ production. Experience through our dry runs in 1.17- 1.20 have shown that
13
13
this slightly "outsider" view helps identify otherwise missed items.
14
14
15
15
More background may be found in the [ PRR KEP] .
@@ -18,8 +18,7 @@ More background may be found in the [PRR KEP].
18
18
19
19
As of 1.21, PRRs are now blocking. PRR _ approval_ is required for the enhancement
20
20
to be part of the release. This means that any KEPs targeting the release for any
21
- stage, and in - or moving to - ` implementable ` state, will require production
22
- readiness approval by the * Enhancements Freeze Date* .
21
+ stage will require production readiness approval by the * Enhancements Freeze Date* .
23
22
24
23
Note that some of the questions in the [ KEP template] should be answered in both
25
24
the KEP's README.md and the ` kep.yaml ` , in order to support automated checks on
@@ -35,7 +34,8 @@ the PRR answers, the authors may request PRR approval:
35
34
* Assign a PRR approver from the ` prod-readiness-approvers ` list in the
36
35
[ OWNERS_ALIASES] file. This may be done earlier as well, to get early feedback
37
36
or just to let the approver know. Reach out on the ` #prod-readiness ` Slack
38
- channel or just pick someone from the list.
37
+ channel or just pick someone from the list. The team may rebalance the
38
+ assignees if necessary.
39
39
* Update the ` kep.yaml ` , setting the ` stage ` , ` latest-milestone ` , and the
40
40
` milestone ` struct (which captures per-stage release versions).
41
41
* Create a ` prod-readiness/<sig>/<KEP number>.yaml ` file, with the PRR
@@ -89,6 +89,6 @@ that need review. For example:
89
89
[ PRR KEP ] : https://git.k8s.io/enhancements/keps/sig-architecture/1194-prod-readiness
90
90
[ KEP template ] : https://git.k8s.io/enhancements/keps/NNNN-kep-template
91
91
[ OWNERS_ALIASES ] : https://git.k8s.io/enhancements/OWNERS_ALIASES
92
- [ example PRR approval request PR ] : https://github.com/kubernetes/enhancements/pull/2274 /files
92
+ [ example PRR approval request PR ] : https://github.com/kubernetes/enhancements/pull/2179 /files
93
93
[ example metrics PR ] : https://github.com/kubernetes/kubernetes/pull/97814
94
94
[ kepctl query ] : https://git.k8s.io/enhancements/cmd/kepctl
0 commit comments