You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What problem are you trying to solve?
We have a ttlSecondsUntilExpired value set on our provisioners so we do not keep really expensive nodes alive for longer than that amount of time. Most of our tasks are short running tasks that fall within the node ttl. Sometimes we do run longer tasks that exceed the ttl. It would be great if we could specify a ttl for when the provisioner will schedule a pod onto the node. For instance, after 3 hours, no nodes will get scheduled onto a Node but all of the tasks currently running on the Node would be allowed to keep running. I have looked through the documentation and haven't been able to find a way to do this. Am I missing something?
Thanks!
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
The text was updated successfully, but these errors were encountered:
Description
What problem are you trying to solve?
We have a ttlSecondsUntilExpired value set on our provisioners so we do not keep really expensive nodes alive for longer than that amount of time. Most of our tasks are short running tasks that fall within the node ttl. Sometimes we do run longer tasks that exceed the ttl. It would be great if we could specify a ttl for when the provisioner will schedule a pod onto the node. For instance, after 3 hours, no nodes will get scheduled onto a Node but all of the tasks currently running on the Node would be allowed to keep running. I have looked through the documentation and haven't been able to find a way to do this. Am I missing something?
Thanks!
The text was updated successfully, but these errors were encountered: