-
Notifications
You must be signed in to change notification settings - Fork 90
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
placement constraints #48
Comments
Current thinking is that node selector, affinity, and labelling for pods are all things that could need to be enforced in the kdapp and/or requested in the kdcluster. We currently have support for the "requested in the kdcluster" part of that story for labels. We should probably extend that to node selector and affinity, and also (for all those things) look into expressing them in the kdapp as well. |
As discussed with @kmathur2 the implementation for now will be adding affinity field as part of RoleSpec specified in kdclusters and passing it to pods. Also a good idea is to add affinity to list of pods in kdclusters' status. The affinity is more advanced and therefore top priority for this feature. Node Selector and Node Name fields can be added later as well. |
#48 Allow specifying Affinity for roles
Think about how we could/should expose affinity and nodeSelector configuration for the deployed pods.
The text was updated successfully, but these errors were encountered: