Epic Goal

• Add UX to the MCE console to allow the user to configure the node selector and tolerations for Klusterlet and addon deployment

Why is this important?

• Red Hat products should be able to deploy to infrastructure nodes, so that the user is not charged for nodes that are designed to host RH workloads
• Customers have requirements to designate a specific node for networking or other security purposes

Scenarios

1. User can go to both the Create cluster or Import cluster pages; and be presented with options to configure the node selector and node tolerations (set annotations on ManagedCluster)
2. User can go to the Cluster details settings page, and see the node selector and toleration configuration for the entire ManagedCluster (annotations on ManagedCluster)
3. User can update the node selector and toleration configurations from the Cluster details settings page for the entire ManagedCluster (annotations on ManagedCluster)

1. User can go to the Cluster details settings page, and see the node selector and toleration configurations for each ManagedClusterAddon (annotations on ManagedClusterAddon)
2. User can update the node selector and toleration configurations from the Cluster details settings page for each ManagedClusterAddon (annotations on ManagedClusterAddon)

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• ...

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. …

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>