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
Describe the bug
The slinkee operator gets stuck deploying a slinkee cluster when there are nodes with taints that will not have a slurmabler deployed on them. The reason is that the operator waits until each node has been labelled, however the slurmabler will not be scheduled on nodes with a taint.
In many Kubernetes clusters the control plane will be tainted so regular workloads cannot be scheduled on them, so on many Kubernetes clusters this will be an issue.
To Reproduce
Steps to reproduce the behavior using a Kind cluster:
Create a kind cluster config for one control plane node and one worker node in /tmp/one-node-kind.yml:
Describe the bug
The slinkee operator gets stuck deploying a slinkee cluster when there are nodes with taints that will not have a slurmabler deployed on them. The reason is that the operator waits until each node has been labelled, however the slurmabler will not be scheduled on nodes with a taint.
In many Kubernetes clusters the control plane will be tainted so regular workloads cannot be scheduled on them, so on many Kubernetes clusters this will be an issue.
To Reproduce
Steps to reproduce the behavior using a Kind cluster:
/tmp/one-node-kind.yml
:Expected behavior
The slinkee operator should ignore the nodes that do not have a slurmabler scheduled on them because of taints.
Additional context
Commit of repo used for testing: 5538806
Kind version: kind v0.22.0 go1.21.7 darwin/arm64
The text was updated successfully, but these errors were encountered: