-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
v0.13.0 pod scheduling fails - didn't match pod affinity rules #2769
Comments
From the information given, I can not tell why this has happened. Do you have a pod from a Did you install the new version, including applying the new RBAC yaml that has added RBAC for creating What you can do is to set the feature-flag |
This may be related to #2768 where I state that it appears that users can only have these names up to 34 chars (or creation of Affinity Assistant will fail) and it appears that your Affinity Assistant Name ended up with a name of 40 chars. If you want, you can try with a shorter name of the pipelinerun name (currently /kind bug |
yep, the affinity assistant cant schedule the pod warning |
Looks like this is a duplicate of #2768, please re-open if not! |
Expected Behavior
pipeline run pod should schedule
Actual Behavior
warning
0/1 nodes are available: 1 node(s) didn't match pod affinity rules, 1 node(s) didn't match pod affinity/anti-affinity.
pod yaml
The text was updated successfully, but these errors were encountered: