Skip to content

OSDOCS-19908-RN: ClusterObjectSet RN#112501

Open
StephenJamesSmith wants to merge 1 commit into
openshift:enterprise-4.22from
StephenJamesSmith:OSDOCS-19908-RN
Open

OSDOCS-19908-RN: ClusterObjectSet RN#112501
StephenJamesSmith wants to merge 1 commit into
openshift:enterprise-4.22from
StephenJamesSmith:OSDOCS-19908-RN

Conversation

@StephenJamesSmith
Copy link
Copy Markdown
Contributor

@StephenJamesSmith StephenJamesSmith commented May 29, 2026

Jira: https://redhat.atlassian.net/browse/OSDOCS-19908

New features and enhancements -> Extensions

Preview: https://112501--ocpdocs-pr.netlify.app/openshift-enterprise/latest/release_notes/ocp-4-22-release-notes.html#ocp-release-notes-extensions_release-notes

Note to Merge Reviewer: All text approved. Current Merge conflict due to link to the main topic isn't working because that topic has not been merged yet. It will be merged for GA and the conflict will resolve.

SME: @perdasilva
QE: @bandrade @grokspawn

@openshift-ci openshift-ci Bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label May 29, 2026
@ocpdocs-previewbot
Copy link
Copy Markdown

ocpdocs-previewbot commented May 29, 2026

@openshift-ci openshift-ci Bot added size/S Denotes a PR that changes 10-29 lines, ignoring generated files. and removed size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels May 29, 2026

ClusterObjectSet API for safe phased rollouts (Technology Preview)::
+
{olmv1-first} introduces the ClusterObjectSet API, which enables safe, phased rollouts of Kubernetes resources during ClusterExtension deployments and upgrades. ClusterObjectSet applies resources sequentially in ordered phases with built-in readiness checks, ensuring dependencies are satisfied before dependent resources are created.
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

I would be careful with the use of "dependencies" here as that can be an overloaded term in the context of OLM (e.g. package dependencies).

@perdasilva
Copy link
Copy Markdown

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label May 29, 2026
@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented May 29, 2026

@StephenJamesSmith: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/validate-portal f9df433 link true /test validate-portal
ci/prow/validate-asciidoc f9df433 link true /test validate-asciidoc

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.

Copy link
Copy Markdown

@bandrade bandrade left a comment

Choose a reason for hiding this comment

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

/lgtm

@StephenJamesSmith
Copy link
Copy Markdown
Contributor Author

/label merge-review-needed

@openshift-ci openshift-ci Bot added needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. merge-review-needed Signifies that the merge review team needs to review this PR labels Jun 1, 2026
@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented Jun 1, 2026

PR needs rebase.

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.

@StephenJamesSmith
Copy link
Copy Markdown
Contributor Author

/retest

@mburke5678 mburke5678 added merge-review-in-progress Signifies that the merge review team is reviewing this PR and removed merge-review-in-progress Signifies that the merge review team is reviewing this PR merge-review-needed Signifies that the merge review team needs to review this PR labels Jun 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

lgtm Indicates that a PR is ready to be merged. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants