Epic Goal

• GA registry+v1 webhook support feature

Why is this important?

• Increases our catalog content coverage surface
• Enables basic functionality, e.g. upgrades through breaking changes with conversion webhooks

Scenarios

1. User installs application with validation webhook configuration(s)
2. User installs application with muting webhook configuration(s)
3. User installs application with CRDs referencing conversion webhooks
4. User installs application with a combination of all webhook types
5. Webhook endpoints are secured with openshift-serviceca generated certificates

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• Openshift enhancement merged
• Feature Gate removed with the following certificate providers: CertManager for upstream and Openshift-ServiceCA for downstream
• Extensive QE

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>