-
Notifications
You must be signed in to change notification settings - Fork 109
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
Add tolerations for targetless agent. #3033
Add tolerations for targetless agent. #3033
Conversation
meowjesty
commented
Jan 23, 2025
- Issue: https://github.com/metalbear-co/operator/issues/737
…ions-tolerate-everything-for-agent
Wait - the sentence in the issue might be tricky but we don't want to use default tolerations on the agent when running targetless. |
What should happen then? I thought it was about: if user sets tolerations in operator.agent-config, use those, otherwise ... do? |
Otherwise don't set tolerations. (only in targetless) |
Alright! |
Removed the default, now it'll just pass the |
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.
Not sure why we even have tolerations 👀 :
The default Kubernetes scheduler takes taints and tolerations into account when selecting a node to run a particular Pod. However, if you manually specify the .spec.nodeName for a Pod, that action bypasses the scheduler
We either:
- (targetless) Don't care about the node at all
- (targeted) Require a specific node and we use
.spec.nodeName
I believe we saw agent pods failing to start because they lacked the tolerations |
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.
Looks good ^^