Open jetdream opened 3 months ago
Hi,
For some reason you got a taint/toleration mismatch between the node and the pod. The node got eee41d49-82a4-4b0b-8488-7e11d8081e77 taint, but the pod was assigned e2721bf3-8294-4ee9-9f48-7aeb33949bb6. This UUID should be the same and it should be UID of the managed pool resource.
Could you provide the logs from the operator pod? That will help to understand what happened.
This operator is what I need! Thank you for your work!
Trying to test based on your example, just slightly modified it for my test cluster. Node pool is successfully created but pod is not scheduled. Could you please check what's wrong?
Error:
0/3 nodes are available: 1 node(s) had untolerated taint {dgolubets.github.io/managed-node-pool: eee41d49-82a4-4b0b-8488-7e11d8081e77}, 2 node(s) didn't match Pod's node affinity/selector. preemption: 0/3 nodes are available: 3 Preemption is not helpful for scheduling
My manifests:
Here is the deployed pod resources: