@@ -53,12 +53,15 @@ denote sections that are under active debate as follows:
53
53
- [ Upgrade/Downgrade Strategy] ( #upgradedowngrade-strategy )
54
54
- [ Production Readiness Review Questionnaire] ( #production-readiness-review-questionnaire )
55
55
- [ Requirements for migration] ( #requirements-for-migration )
56
+ - [ Feature Enablement and Rollback] ( #feature-enablement-and-rollback )
56
57
- [ Rollout, Upgrade and Rollback Planning] ( #rollout-upgrade-and-rollback-planning )
57
58
- [ Monitoring Requirements] ( #monitoring-requirements )
58
59
- [ Dependencies] ( #dependencies )
59
60
- [ Scalability] ( #scalability )
60
61
- [ Troubleshooting] ( #troubleshooting )
61
62
- [ Implementation History] ( #implementation-history )
63
+ - [ Drawbacks] ( #drawbacks )
64
+ - [ Alternatives] ( #alternatives )
62
65
<!-- /toc -->
63
66
## Release Signoff Checklist
64
67
@@ -208,6 +211,9 @@ However any HPA objects stored in the user's code repository (all your YAML file
208
211
v2beta1 format. You should migrate all your HPA objects to the v2 format. See the types.go files or just
209
212
run ` kubectl get hpa.v2.autoscaling -oyaml ` to see your objects in the v2 format.
210
213
214
+ ### Feature Enablement and Rollback
215
+ N/A
216
+
211
217
###### Does enabling the feature change any default behavior?
212
218
213
219
<!--
@@ -567,3 +573,7 @@ For each of them, fill in the following information by copying the below templat
567
573
* Container Resource Targets
568
574
* [ Proposed] ( https://github.com/kubernetes/enhancements/blob/master/keps/sig-autoscaling/0001-container-resource-autoscaling.md ) on Mar 30, 2020
569
575
(Implementation is pending)
576
+
577
+ ## Drawbacks
578
+
579
+ ## Alternatives
0 commit comments