Skip to content
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

Adding self taint toleration for wasp-agent deployment #75

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

enp0s3
Copy link
Member

@enp0s3 enp0s3 commented Oct 9, 2024

Signed-off-by: Igor Bezukh [email protected]

When node is under pressure and we evict pods, we also taint the node. If for some reason wasp-agent would be restarted, the wasp-agent pod won't be able to run on a tainted node.

This is bad since wasp-agent needs to complete the eviction process, and clear the taint as far as node resources are stable again.

enp0s3 added 2 commits October 9, 2024 09:58
taint logic needs to be synced with the operator
that generates the wasp-agent ds manifest, because
wasp-agent needs to tolerate its own taint.

this is needed in case wasp-agent pod will be
restarted while the node is tainted. wasp-agent
needs to complete its eviction operation and remove
the taint when resources are back to normal.

Signed-off-by: Igor Bezukh <[email protected]>
added self taint toleration to the wasp-agent ds yaml.

Signed-off-by: Igor Bezukh <[email protected]>
Copy link

openshift-ci bot commented Oct 9, 2024

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from enp0s3. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Copy link
Member

@Barakmor1 Barakmor1 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you!

@Barakmor1
Copy link
Member

Barakmor1 commented Nov 19, 2024

@enp0s3 We need a follow up PR for the docs

edit: never-mind i just realized that we refer users to ds.yaml

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants