Epic Goal

• Deploy add-on agents to the nodes that meet the node selector and toleration criteria

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. Add-on agents will deploy to the nodes following the node selector and toleration configurations
   1. Submariner agent
   2. ??

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• All add-ons owned by team adopt the node selector and toleration configurations.

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>