Epic Goal

• Argo Rollouts supports plugins for a variety of use cases including traffic managers (https://argoproj.github.io/argo-rollouts/features/traffic-management/plugins) and metrics (https://argoproj.github.io/argo-rollouts/analysis/plugins)
• The operator should suppport users being able to quickly and easily add these plugins in the operator
• Traditionally these plugins support being installed in the rollouts controller via mounts or remote, both styles should be supported.

Why is this important?

• Customers typically have a wide range of infrastructure and having the ability to either write or use existing plugins enables Rollouts to work with this infrastructure.

Scenarios

1. Customer wants to deploy a traffic management plugin in Rollouts
2. Customer wants to deploy a metrics plugin in Rollouts

Acceptance Criteria (Mandatory)

• 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

• Acceptance criteria are met
• Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
• User Journey automation is delivered
• Support and SRE teams are provided with enough skills to support the feature in production environment