-
Notifications
You must be signed in to change notification settings - Fork 40k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Increase default value of apps/v1beta2 DeploymentSpec.RevisionHistoryLimit to 10 #49924
Increase default value of apps/v1beta2 DeploymentSpec.RevisionHistoryLimit to 10 #49924
Conversation
@dixudx: GitHub didn't allow me to request PR reviews from the following users: liyinan926. Note that only kubernetes members can review this PR, and authors cannot review their own PRs. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Hi @dixudx. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
@dixudx We only plan to do this for |
8434913
to
ebd8ac7
Compare
@liyinan926 Updated. PTAL. Thanks. |
LGTM. |
@tsmetana can you take a look here? |
Wrong Tomas it seems. @tnozicka ptal |
Ref kubernetes/enhancements#353 @dixudx @liyinan926 I don't see this mentioned in #49135 Also, default values should be documented in the API documentation in the field comments in v1beta2/types.go. Both the API documentation and the release note should be written for Kubernetes users, not just for Kubernetes contributors, which means they should use the json names, not Go type/field names. |
@bgrant0607 this is part of the work on "ensure that the defaults and validation are consistent and appropriate across all controllers." mentioned in #49135. #49913 has more details on inconsistency of the default value of |
/ok-to-test |
/lgtm |
@liyinan926: changing LGTM is restricted to assignees, and only kubernetes org members may be assigned issues. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/assign mml janetkuo saad-ali kow3ns |
/unassign wojtekt |
👎 /unassign wojtek-t |
OK, after all those gymnastics, it looks like @kow3ns has this under control. /unassign |
@thockin @smarterclayton Needs your |
/approve |
FWIW the corr3ct protocol would be to |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dixudx, kow3ns, liyinan926, thockin Associated issue: 49913 The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
/retest |
Automatic merge from submit-queue |
…figs Automatic merge from submit-queue Set default for DeploymentConfigSpec.RevisionHistoryLimit in apps/v1 At this point we don't default DeploymentConfigSpec.RevisionHistoryLimit in apps/v1 which is causing the deployments to have unlimited history which will lead to performance issues at scale and when deploying regularly. Note that upstream also defaulted RevisionHistoryLimit to 10 for Deployments in kubernetes/kubernetes#49924 Needs to be backported to 3.6.1 as well. cc: @smarterclayton @mfojtik @Kargakis
What this PR does / why we need it:
All controllers that use the
RevisionHistoryLimit
field have a default value of 10 for the field, except forDeployment
, which has a default of 2. We should increase it to 10 for consistency on its default value across controllers.Which issue this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close that issue when PR gets merged): fixes #49913Special notes for your reviewer:
/cc @janetkuo @foxish @liyinan926
Release note: