WHAT

A new release for the Observability Operator (v3.0.13) should be created.

WHY

Recent additions (including fix for duplicate PVC creation when Operator is running as self-contained) are required by teams using the Operator.

HOW

A new release needs to be prepared in both upstream and midstream repos.

DONE

• New release (v3.0.13) available from both midstream and upstream

Guidelines

The following steps should be adhered to:

• Required tests should be put in place - unit, integration, manual test cases (if necessary)
• CI and all relevant tests passing
• Changes have been verified by one additional reviewer against:
• each required environment
• each supported upgrade path
• If the changes could have an impact on the clients (either UI or CLI), a JIRA should be created for making the required changes on the client side and acknowledged by one of the client side team members. PR has been merged