Skip to content

Patch tigera-operator deployment to rm NoSchedule toleration#5990

Merged
GeorgianaElena merged 1 commit into
2i2c-org:mainfrom
GeorgianaElena:rm-tigera-toleration
Apr 30, 2025
Merged

Patch tigera-operator deployment to rm NoSchedule toleration#5990
GeorgianaElena merged 1 commit into
2i2c-org:mainfrom
GeorgianaElena:rm-tigera-toleration

Conversation

@GeorgianaElena

Copy link
Copy Markdown
Member

Fixes #5961

@github-actions

This comment was marked as resolved.

"template": {
"spec": {
"tolerations": [
{"effect": "NoExecute", "operator": "Exists"},

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

This is coming from https://github.com/projectcalico/calico/blob/da6b089ff18f2e4ab104def0f78e68c8741fc221/manifests/tigera-operator.yaml#L535-L539

Wasn't sure if I should keep it, but for now it doens't bother us I think

@GeorgianaElena GeorgianaElena merged commit 6547920 into 2i2c-org:main Apr 30, 2025
39 checks passed
@GeorgianaElena GeorgianaElena deleted the rm-tigera-toleration branch April 30, 2025 09:18
@github-actions

Copy link
Copy Markdown
Contributor

🎉🎉🎉🎉

Monitor the deployment of the hubs here 👉 https://github.com/2i2c-org/infrastructure/actions/runs/14751144406

@yuvipanda

Copy link
Copy Markdown
Member

I think this is sufficient, but can you change the comment in --force-apply to no longer say 'remove this after some task is done' but to document why we need it? Given we want the source of truth to be that apply, and our patch is minor afterwards, this feels fine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[AWS] tigera-operator gets deployed on user nodes blocking scale downs

2 participants