Skip to content

Conversation

@michaelryanpeter
Copy link
Contributor

@michaelryanpeter michaelryanpeter commented Jan 23, 2026

@michaelryanpeter michaelryanpeter added this to the Planned for 4.21 GA milestone Jan 23, 2026
@openshift-ci openshift-ci bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Jan 23, 2026
@ocpdocs-previewbot
Copy link

ocpdocs-previewbot commented Jan 23, 2026

🤖 Tue Jan 27 21:44:29 - Prow CI generated the docs preview:

https://105321--ocpdocs-pr.netlify.app/openshift-enterprise/latest/release_notes/ocp-4-21-release-notes.html

@michaelryanpeter michaelryanpeter force-pushed the ocp-4.21-olm-release-notes branch from 0d44d9e to c65545c Compare January 23, 2026 20:12
@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jan 23, 2026
@michaelryanpeter michaelryanpeter force-pushed the ocp-4.21-olm-release-notes branch from c65545c to d0c6d59 Compare January 23, 2026 20:15
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jan 23, 2026
@michaelryanpeter
Copy link
Contributor Author

cc: @opayne1 and @jseseCCS

@jianzhangbjz
Copy link
Member

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 26, 2026
@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jan 27, 2026
@michaelryanpeter michaelryanpeter force-pushed the ocp-4.21-olm-release-notes branch from d0c6d59 to 7ccaf1b Compare January 27, 2026 15:47
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Jan 27, 2026
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jan 27, 2026
@oceanc80
Copy link

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 27, 2026
@michaelryanpeter
Copy link
Contributor Author

/retest-required

@mkumku
Copy link

mkumku commented Jan 27, 2026

LGTM. Thanks!

@michaelryanpeter
Copy link
Contributor Author

/label merge-review-needed

@openshift-ci openshift-ci bot added the merge-review-needed Signifies that the merge review team needs to review this PR label Jan 27, 2026
@stevsmit stevsmit added merge-review-in-progress Signifies that the merge review team is reviewing this PR and removed merge-review-needed Signifies that the merge review team needs to review this PR labels Jan 27, 2026
////
Cluster extension support for webhooks in bundles::
+
With this update, {olmv1} supports Operators that use webhooks for validation, mutation, or conversion. For more information, see xref:..//extensions/ce/olmv1-supported-extensions.adoc#olmv1-webhook-support_olmv1-supported-extensions[Webhook support].
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure if it's intended but this link doesn't work. Also I noticed that there's two // before extensions.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

stray / was my fault. but the other issue was that I forgot to rebase and push after the docs merged. so the xrefs passed the build but I didn't have the updated docs rendered in my preview.


Support for `SingleNamespace` and `OwnNamespace` install modes by using the configuration API (Technology Preview)::
+
With this update, you can configure watch namespaces for Operators that support the `SingleNamespace` and `OwnNamespace` install mode. For more information, see xref:../extensions/ce/olmv1-configuring-extensions.adoc#olmv1-config-api_olmv1-configuring-extensions[Extension configuration].
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is ". . . you can configure watch namespaces. . ." grammatically correct? maybe I don't understand the feature. This xref doesn't work either (might be intentional).

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Rephrased to:

"If an Operator supports the SingleNamespace or OwnNamespace install modes, you can configure the Operator to watch a specified namespace."

@michaelryanpeter michaelryanpeter force-pushed the ocp-4.21-olm-release-notes branch from 7ccaf1b to 086eddd Compare January 27, 2026 21:36
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Jan 27, 2026
@openshift-ci
Copy link

openshift-ci bot commented Jan 27, 2026

New changes are detected. LGTM label has been removed.

@openshift-ci
Copy link

openshift-ci bot commented Jan 27, 2026

@michaelryanpeter: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@michaelryanpeter michaelryanpeter merged commit 50e149d into openshift:enterprise-4.21 Jan 28, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

branch/enterprise-4.21 merge-review-in-progress Signifies that the merge review team is reviewing this PR size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants