-
Notifications
You must be signed in to change notification settings - Fork 89
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
Node Selector doesn't get applied on K8s platforms #462
Comments
@juanpablo-santos Thank you for reporting this issue: We will work on resolving this bug. |
Hi @cppwfs! thanks a lot for the workaround :-) I did try the property, but instead of using cheers, |
Thanks @juanpablo-santos for doing the legwork. |
Hi @corneil! saw the associated PR, would that cover the platform property as well? i.e., thanks for looking into this so fast :-) |
Description:
per title, Node Selector configuration option doesn't get applied on K8s platforms, neither by setting
spring.cloud.dataflow.task.platform.kubernetes.XXXX.deployment.nodeSelector
nor by applying the configuration on task execution, through the UI (thedeployer.XXXXXX.kubernetes.node-selector=NAME:VALUE
)Release versions:
Custom apps:
N/A, issue is reproduced with any task execution.
Steps to reproduce:
Neither setting
spring.cloud.dataflow.task.platform.kubernetes.XXXX.deployment.nodeSelector: "NAME:VALUE"
nor by applying the configuration on task execution, through the UI (thedeployer.XXXXXX.kubernetes.node-selector=NAME:VALUE
.Screenshots:
Additional context:
Saw PR spring-cloud/spring-cloud-dataflow#301, the configuration provided there also doesn't work
The text was updated successfully, but these errors were encountered: