Expose nodeSelector in knative-operator Helm chart

[chenrui333]

Problem

The knative-operator Helm chart exposes affinity and tolerations for both chart-owned deployments:

• knative_operator.knative_operator.affinity
• knative_operator.knative_operator.tolerations
• knative_operator.operator_webhook.affinity
• knative_operator.operator_webhook.tolerations

It does not expose matching nodeSelector values for those same deployments.

Clusters with dedicated node pools often need all three scheduling knobs. Today the workaround is to express simple node selection through affinity.nodeAffinity, which works but is more verbose and less consistent with common Helm chart behavior.

Request

Add nodeSelector support for both chart-owned deployments:

• knative_operator.knative_operator.nodeSelector
• knative_operator.operator_webhook.nodeSelector

and render those values into spec.template.spec.nodeSelector.

Related

• Operations: Please allow setting nodeSelector, tolerations, and affinity on all Pods #5 requested nodeSelector, tolerations, and affinity support broadly.
• Allow to set NodeSelector via spec.deployments.nodeSelector #658 added spec.deployments.nodeSelector support for KnativeServing/KnativeEventing workloads managed by the operator.
• Enable the support of NodeSelectors and tolerations on Jobs #1479 / Add the ability to configure tolerations and nodeselector for Knative pre/post-install jobs #1480 added nodeSelector and toleration support for migration jobs.

This issue is narrower: it only covers the Helm chart's own operator and webhook deployment pods.

[github-actions]

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.