-
Story
-
Resolution: Unresolved
-
Undefined
-
Gatekeeper 3.18.0
Epic Goal
When Gatekeeper 3.18 is released, let's update the Gatekeeper operator.
Why is this important?
It's important to stay up to date with upstream to provide the latest features and fixes to customers while also reducing backport/maintenance burden on the team.
Scenarios
...
Acceptance Criteria
The Gatekeeper operator is updated to deploy Gatekeeper 3.17.
Dependencies (internal and external)
- Hybrid build team needs to set up downstream configuration
Previous Work (Optional):
- ...
Open questions:
- …
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 - Doc issue opened with a completed template. Separate doc issue
opened for any deprecation, removal, or any current known
issue/troubleshooting removal from the doc, if applicable.