Skip to content

OSDOCS-15331 OSUS single stream release additional text #96185

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

cbippley
Copy link
Contributor

@cbippley cbippley commented Jul 16, 2025

@openshift-ci openshift-ci bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Jul 16, 2025
@ocpdocs-previewbot
Copy link

ocpdocs-previewbot commented Jul 16, 2025

Copy link

openshift-ci bot commented Jul 17, 2025

@cbippley: all tests passed!

Full PR test history. Your PR dashboard.

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.

@@ -17,6 +17,10 @@ keep your cluster up to date with the most recent compatible components.

To allow the OpenShift Update Service to provide only compatible updates, a release verification pipeline drives automation. Each release artifact is verified for compatibility with supported cloud platforms and system architectures, as well as other component packages. After the pipeline confirms the suitability of a release, the OpenShift Update Service notifies you that it is available.

The OpenShift Update Service (OSUS) supports a single-stream release model, where only one release version is active and supported at any given time. When a new release is deployed, it fully replaces the previous release.

The updated release provides support for upgrades from all {product-title} versions starting after 4.10 up to the new release version.
Copy link

Choose a reason for hiding this comment

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

It means the latest released osus support v4.10+ ocp versions, right? Currently, the supported ocp version from osus build config is 4.8, while 4.12 is the oldest supported ocp version in eus term2. Not sure whether 4.8 or 4.12 is more suitable to replace 4.10.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@jiajliu I've been told that 4.10 is correct because of some api removals, etc. It does not have to do with OCP versions. They want to support as far back as they can.

Copy link

@jiajliu jiajliu Jul 21, 2025

Choose a reason for hiding this comment

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

LABEL com.redhat.openshift.versions=v4.8

^^ is the current configuration in osus dockerfile. It indicates that the furthest supported ocp version is 4.8(actually it's EOL), the inconsistency between the documentation and the product might make confusion to users. I did not hear that we planned to update the dockerfile to 4.10 in next release. Maybe we should confirm with dev on the inconsistency.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants