Closed juanpablo-santos closed 3 months ago
@juanpablo-santos Thank you for reporting this issue:
A work around is to set the following property for node selectors: deployer.<appname>.kubernetes.deployment.nodeSelector=foo:bar
We will work on resolving this bug.
Hi @cppwfs! thanks a lot for the workaround :-)
I did try the property, but instead of using nodeSelector
I did use node-selector
(as generated by the UI), thought they were interchangeable and didn't thought on using nodeSelector
. In any case, the workaround is more than enough for us until the issue is fixed.
cheers, juan pablo
Thanks @juanpablo-santos for doing the legwork.
We will be fixing that one since was expecting a property named with nodeSelector
instead of allowing node-selector
.
Hi @corneil! saw the associated PR, would that cover the platform property as well? i.e., spring.cloud.dataflow.task.platform.kubernetes.XXXX.deployment.nodeSelector
also doesn't get assigned
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