-
Notifications
You must be signed in to change notification settings - Fork 545
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
fix: add autoscaling eviction annotation to catalog pods #2669
fix: add autoscaling eviction annotation to catalog pods #2669
Conversation
0719e92
to
9a67c3b
Compare
/approve @exdx could you please rebase? |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: exdx, perdasilva 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 |
9a67c3b
to
b75bbd8
Compare
done -- I think this is a reasonable stop-gap solution for our upstream users until we come up with a better story around how we want to support catalog pods being evicted from nodes during a drain or node scale down event. If we come up with a more robust solution, this annotation still should not be prohibitive. |
b75bbd8
to
ced96dc
Compare
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.
from the autoscaler side, +1, thank you for adding this.
/lgtm |
ced96dc
to
cf6c8e2
Compare
Rebasing off HEAD of master |
…oper draining of nodes Signed-off-by: Daniel Sover <dsover@redhat.com>
cf6c8e2
to
2968449
Compare
/lgtm |
Does this make node draining work too? In that past that hasnt worked. Though I haven't tested on the newest olms. |
Unfortunately no, the catalogsource pod preventing node draining is still an issue. We are tracking that effort in an RFE https://issues.redhat.com/browse/RFE-2737. |
Signed-off-by: Daniel Sover dsover@redhat.com
Description of the change:
Closes #2666
Because the catalog pods are standalone and not backed by a Deployment/ReplicaSet, it causes issues when draining the underlying node, when then affects autoscaling. This additional annotation on the catalog pods will enable the cluster autoscaler to evict catalog pods when draining a node.
Motivation for the change:
Enable cluster autoscaling to work
Reviewer Checklist
/doc
[FLAKE]
are truly flaky[FLAKE]
tag are no longer flaky