Feature Overview
Upgrade the rabbitmq-cluster Operator to a more recent version within the RHOSO 18 environment.

Goals

• The rabbitmq-cluster Operator has been rebased to a recent release that matches development teams expectations.
• New content has been imported and built, ready to ship by production chain teams.
• Automated testing environments have been updated to use the new version and are passing.

Requirements

Done - Acceptance Criteria
The rabbitmq-cluster Operator has been updated both upstream and is imported and building downstream. Version bumps have been provided in appropriate locations in the code base in preparation for delivery to customers.

Use Cases - i.e. User Experience & Workflow
N/A

Out of Scope
Implementation of any new functionality provided within the rabbitmq-cluster Operator. Expectation is this is a simple version bump to a more recent version in preparation for use of extra features in the future.

Documentation Considerations
No new documentation should be required. Only release note updates.

Questions to Answer
N/A

Background and Strategic Fit
N/A

Customer Considerations

• There is an expectation that a period of downtime will be required and need to be scheduled as part of the RHOSO update.

Team Sign Off (Completion while in Planning status)

• All required Epics (known at the time) are linked to the this Feature
• All required Stories, Tasks (known at the time) for the most immediate Epics have been created and estimated
• Add - Reviewers name, Team Name
• Acceptance == Feature as “Ready” - well understood and scope is clear - Acceptance Criteria (scope) is elaborated, well defined, and understood
• Note: Only set FixVersion/s: on a Feature if the delivery team agrees they have the capacity and have committed that capability for that milestone

• …