Epic Goal

The following features MUST be completed to make sure Pruner is GA ready

• Include a webhook validation to ensure data type validation for values set in the configmap (Pruner settings)
• complete and thoroughly assess the pruner controller behavior with annotation and label based configuration
• Allow granular config map based configuration at individual namespace level. If a config map is defined at a namespace level than the namespace level config will take precedence over the global config map settings specific to the namespace in open shift-pipelines namespace
• Enable complete config management of pruner config from tekton config (This is a change to the current operator behavior which just allows enable/disable)
• Include detailed observability  metrics for pruner.

Why is this important?

Scenarios

1. ...

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