-
Notifications
You must be signed in to change notification settings - Fork 350
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
Ability to define K8s toleration for Builder pod #5354
Comments
Thanks for reporting. If you think you can contribute by any chance, just let us know. |
I think I can contribute on this one. Let me know if you can give me some more information where to start, it would speed up my work.
Thanks,
Vlad
… On 11. 4. 2024, at 13:05, Pasquale Congiusti ***@***.***> wrote:
Thanks for reporting. If you think you can contribute by any chance, just let us know.
—
Reply to this email directly, view it on GitHub <#5354 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAFNNQHTS5EJL5UUBB536EDY4ZU53AVCNFSM6AAAAABGCBPCCKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANBZGQ2DCMZZGU>.
You are receiving this because you authored the thread.
|
Cool. So, probably you can mimic the work done in #4968 where we were adding the NodeSelector. The logic would be the same, but, with the new field instead. Feel free to ask any support here or in zulip chat [1] where we can have a quicker interaction. [1] https://camel.zulipchat.com/#narrow/stream/257299-camel-k |
@squakez I will look into this one if that's okay. |
I'm just starting to work on this one.. |
Hello @vkrejcirik are you still actively working on this? |
Requirement
I'm trying to define K8s toleration for Builder pod when using Native build. I want to dedicate nodes for Native builds. Builder trait allows to define node selector, but not toleration.
Problem
When having nodes with taints, I cannot schedule Builder pods on these nodes.
Proposal
I suggest adding new parameter to Builder trait which would allow adding toleration to the Builder pod.
Open questions
No response
The text was updated successfully, but these errors were encountered: