-
Notifications
You must be signed in to change notification settings - Fork 67
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
Controller states: "Not enough available nodes" #440
Comments
I guess eu-west has a different zone from the eu-central nodes. The problem is that it first locks in a preferred node (eu-west), and then tries to place the rest. This then fails because there are not enough nodes in that zone. By the way, you dont need specify the placement on different nodes with kubernetes.io/hostname, that is always implied. |
I just removed the eu-west node from the cluster. Still getting same error:
|
Well, are the nodes actually in the same zone? Perhaps they are in the same region, but different zones? |
Ah.. Yes Two of them are! The third one isn't: Also I had an nodeAffinity defined causing it to schedule one of the single zone servers:
Mystery solved!🕵️ Thanks |
I have Stateful that's not able to deploy. See information below.
PVC event:
Controller logs:
I am able to create resources manually:
The text was updated successfully, but these errors were encountered: