WHAT

A new release for the Observability Operator (v4.1.0) should be created.

WHY

A number of recent changes are ready to be released including support for reading observability configuration from container.

HOW

• Install/upgrade and feature verification checks should be made.
• Operator version in KFM upstream should be bumped. See similar version bump PR for guidance
• Operator version in KFM SAAS file should also be bumped. See similar version bump MR for guidance

DONE

• New release (v4.1.0) available from both midstream and upstream
• Operator version bumped in KFM upstream and in SAAS file

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