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
Currently, user pods only carry a toleration for the default renku user node taint, but no corresponding node affinity or node-selector is added. Hence, when user nodes fill up, user sessions are happily scheduled onto non-user nodes. Ideally, it would be fully configurable through the chart along those lines:
which labels must be present on a node for a user session to be allowed to run on it (default none)
and
which taints can be present on a node for a user-session to be still run on it (ie tolerate it) (default: renku.io/dedicated=user:NoSchedule)
The text was updated successfully, but these errors were encountered:
Currently, user pods only carry a toleration for the default renku user node taint, but no corresponding node affinity or node-selector is added. Hence, when user nodes fill up, user sessions are happily scheduled onto non-user nodes. Ideally, it would be fully configurable through the chart along those lines:
and
renku.io/dedicated=user:NoSchedule
)The text was updated successfully, but these errors were encountered: