Epic Goal

• Provide a global configuration for an add-on to allow it to be automatically installed in a cluster if it meets a specified criteria.

Why is this important?

• When a cluster is registered into RHACM, we will want all desired management functions to be automatically enabled.
  • For example, a cluster may meet the the Placement criteria for a Policy to be deployed into the cluster; but the Policy add-on may not be installed.
• Currently, we have a disparate add-on installation experience.
  • Some add-ons are enabled through the KlusterletAddOnConfig CR that must be created in each ManagedCluster namespace.
  • Other add-ons are enabled in an all or nothing fashion, like the cluster-proxy add-on.

Scenarios

Community Proposal

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>