fix: add linux node selector to deployments

[pzerelles]

When KEDA is deployed to a mixed Kubernetes cluster with linux and windows nodes, the deployments did not select the linux nodes explicitly and could not be started on windows nodes.

Checklist

• I have verified that my change is according to the deprecations & breaking changes policy
• Commits are signed with Developer Certificate of Origin (DCO - learn more)
• [-] README is updated with new configuration values (if applicable) learn more
• [-] A PR is opened to update KEDA core (repo) (if applicable, ie. when deployment manifests are modified)

[JorTurFer]

Hi
Have you faced with KEDA or with the HTTP Add-on chart? KEDA chart already has the node selector

• https://github.com/kedacore/charts/blob/main/keda/templates/manager/deployment.yaml#L194-L195
• https://github.com/kedacore/charts/blob/main/keda/templates/metrics-server/deployment.yaml#L182-L183
• https://github.com/kedacore/charts/blob/main/keda/templates/webhooks/deployment.yaml#L149-L150

[JorTurFer]

We are cutting a release of the HTTP add-on right now, so I have just included the missing node selector within it
#543

[pzerelles]

Hi,I actually added it to both, but maybe I missed something in keda core.Thanks for adding it to the html-add-on release!Philipp Am 2023. 10. 05. um 15:02 schrieb Jorge Turrado Ferrero ***@***.***>: Hi Have you faced with KEDA or with the HTTP Add-on chart? KEDA chart already has the node selector —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[JorTurFer]

I close this as I have included your changes in that PR in progress (it's faster than fix your PR, merge it and update the other). Thanks for the PR in any case