Epic Goal

• Support configuring nodeSelector and tolerations for klusterlet and addons from API

https://github.com/stolostron/backlog/issues/20569#issuecomment-1083919366

Why is this important?

• OpenShift customers should be able to run product related workloads on specific infrastructure nodes, so that they are not getting billed for compute, network, and storage services utilized by our deployments
• Some customers need a workload to run on specific nodes, because they want to secure the networking on most of the cluster's nodes; and only open up the network for the nodes that will run workloads that require it.

Scenarios

1. User can define nodeSelector to delegate placement of Klusterlet and all add-ons to specific nodes
2. User can define tolerations to delgate placement of Klusterlet and all add-ons to nodes with specified taints

Acceptance Criteria

• User can define nodeSelector to delegate placement of Klusterlet and all add-ons to specific nodes
• User can define tolerations to delgate placement of Klusterlet and all add-ons to nodes with specified taints
• Documented in official product documentation
• Technical enablement provided

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. NodeSelect is a defined Kuberenetes key/value pair for pods, since this sets a precedence for the user experience, make sure consistent usability is maintained.
2. Tolerations is a defined Kuberenetes key/value pair, since this sets a precedence for the user experience, make sure consistent usability is maintained.

Open questions::

1. …

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>