-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
deploy: drop unnecessary resource handlers to reduce dc requeues #11805
Conversation
No reason to enqueue deployment configs on rc ADDs since there is no new info deployment configs don't know at that point (adoption is not possible). No reason to enqueue on pod ADDs since the only reasons we need pod notification are 1) to bring back DELETEd pods and 2) to update the deployment config status with AvailableReplicas once a pod is UPDATEd to Ready/Available.
[test] |
Can somebody from @openshift/team-origin-committers rekick Jenkins? |
Evaluated for origin test up to 5109853 |
continuous-integration/openshift-jenkins/test SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/11933/) (Base Commit: 1023112) |
LGTM since adoption is not possible. [merge] |
flake is #12157 |
[merge] |
#12184 [merge] |
continuous-integration/openshift-jenkins/merge SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/11933/) (Image: devenv-rhel7_5515) |
#8571 [merge] |
Evaluated for origin merge up to 5109853 |
No reason to enqueue deployment configs on rc ADDs since there is no
new info deployment configs don't know at that point (adoption is not
possible). No reason to enqueue on pod ADDs since the only reasons we
need pod notification are 1) to bring back DELETEd pods and 2) to
update the deployment config status with AvailableReplicas once a pod
is UPDATEd to Ready/Available.
cc: @mfojtik @smarterclayton
[test]