-
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
Deployment to stop adding pod-template-hash labels/selector on adoption #61615
Conversation
/lgtm |
You may have to fix e2e tests |
/lgtm Are you planning on making Deployment selectors immutable in a future release? |
|
Found some functions not referenced by anyone after removing |
It seems that
So I'll leave |
Integration test failure is observed in other PRs too. Should be a flake unrelated to this PR. Filed #61748. |
/test pull-kubernetes-integration |
All green. @Kargakis PTAL |
/lgtm |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
we might want to have a issue tracking deprecation and removal for RSs created directly by the deployment
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: janetkuo, kargakis, tnozicka The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Automatic merge from submit-queue (batch tested with PRs 61790, 61808, 60339, 61615, 61757). If you want to cherry-pick this change to another branch, please follow the instructions here. |
What this PR does / why we need it: This is a blocker for #55714, because ReplicaSet selector becomes immutable in
apps/v1
. With controller ref, Deployment's ReplicaSets and Pods can avoid fighting with each others without unique label/selector (pod-template-hash), so it's safe to stop adding hash label/selector on adoption.Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #61433
Special notes for your reviewer: This is a behavioral change to Deployment controller that will affect all versions of Deployment APIs (
apps/v1
,extensions/v1beta1
,apps/v1beta1
,apps/v1beta2
).Release note: