Follow up on the following message:

We are now launching Phase 2, focusing on operators that use webhook definitions and the SingleNamespace/OwnNamespace install modes.

Please verify that your relevant operator runs correctly under OLMv1 using the instructions in the Verifying Published Content with OLM v1 document.

We must receive your results by November 21, 2025, to ensure all required fixes on the OLM side are merged into OCP 4.21 before the December 5th Feature Freeze.

Please respond to this email to confirm you've received it and feel free to reach out if you have any questions or concerns via #olm-v1-adoption-for-your-operator.

Note:

If this request is better directed to someone else, we’d appreciate your guidance and redirection on the appropriate contact.

Join the Program Communication Channels to receive important updates!

We want to ensure you have all the latest information and can engage directly with the team.

Mailing List: operatorframework-pgm@redhat.com

Slack Channel: #forum-operator-fw-program

The relevant document mentioned is the following:
https://docs.google.com/document/d/1UpBLZFGONj-e9aDTvWFdlGKLnaIhTZQr-wOWcs6lGCI/edit?tab=t.0#heading=h.y02czw19ankp

• As reference, here are some similar tickets beign assigned to other teams: https://issues.redhat.com/browse/CNV-71372 and https://issues.redhat.com/browse/SECURESIGN-3180