@@ -133,7 +133,7 @@ Items marked with (R) are required *prior to targeting to a milestone / release*
133
133
- [x] (R) Test plan is in place, giving consideration to SIG Architecture and SIG Testing input
134
134
- [x] (R) Graduation criteria is in place
135
135
- [x] (R) Production readiness review completed
136
- - [ ] Production readiness review approved
136
+ - [x ] Production readiness review approved
137
137
- [ ] "Implementation History" section is up-to-date for milestone
138
138
- [ ] User-facing documentation has been created in [ kubernetes/website] , for publication to [ kubernetes.io]
139
139
- [ ] Supporting documentation—e.g., additional design documents, links to mailing list discussions/SIG meetings, relevant PRs/issues, release notes
@@ -463,13 +463,16 @@ you need any help or guidance.
463
463
464
464
### Feature Enablement and Rollback
465
465
466
- As an addition to Kubernetes testing, enablement and rollback are managed
467
- by configuration changes in ` kubernetes/test-infra ` .
466
+ As part of Prow, enablement is managed by configuration in ` kubernetes/test-infra ` .
467
+ As the test target and tool version are fixed in ` kubernetes/kubernetes/hack/tools ` ,
468
+ rollback can be handled by reverting any offending commit to ` hack/tools ` .
468
469
469
470
### Rollout, Upgrade and Rollback Planning
470
471
471
472
As a third-party dependency, analyzer upgrading is handled by upgrading
472
- the version targeted by ` kubernetes/kubernetes/hack/tools/ ` .
473
+ the version targeted by ` kubernetes/kubernetes/hack/tools/ ` .
474
+ Tool configuration at ` kubernetes/kubernetes/hack/testdata/levee ` can be updated
475
+ independently, though may be required during tool upgrading.
473
476
474
477
### Monitoring Requirements
475
478
0 commit comments