Dapr: Node Selector for Helm Install on Kubernetes w/ Windows Nodes

[cwiederspan]

Is there a way to set a node selector when installing the dapr runtime on a Kubernetes cluster that includes a Windows node pool?

Without it, it's trying to put my dapr-system pods onto Windows nodes.

Thanks for any pointers or help.

[youngbupark]

linking #842

@cwiederspan We're prioritizing the work to run dapr on windows nodes.

cc/ @msfussell @orizohar @yaron2 @amanbha

[youngbupark]

@msfussell @orizohar @yaron2 @amanbha Do we deliver windows container image in this milestone?

[yaron2]

@msfussell @orizohar @yaron2 @amanbha Do we deliver windows container image in this milestone?

I think we should. It's not a lot of work and would open up more scenarios.

[amanbha]

@msfussell @orizohar @yaron2 @amanbha Do we deliver windows container image in this milestone?

I think we should. It's not a lot of work and would open up more scenarios.

Yes, lets do it in 0.9.0

[youngbupark]

we also need to set up windows node aks to run e2e tests..

[asumner]

@cwiederspan > Is there a way to set a node selector when installing the dapr runtime on a Kubernetes cluster that includes a Windows node pool?

Without it, it's trying to put my dapr-system pods onto Windows nodes.

Thanks for any pointers or help.

We set a taint on the windows nodes to block dapr from scheduling to them. Then they all deployed to linux nodes.

[youngbupark]

Let's discuss it more on #842 and mark this as 0.9.0 release.

I am closing this issue as a dupe - https://github.com/dapr/dapr/issues/842