Skip to content

OCPBUGS-122280: Document mirror registry version support and lifecycle policy - #119725

Open
Pratik-Redhat-Tech wants to merge 1 commit into
openshift:mainfrom
Pratik-Redhat-Tech:doc-mirror-registry-lifecycle
Open

OCPBUGS-122280: Document mirror registry version support and lifecycle policy#119725
Pratik-Redhat-Tech wants to merge 1 commit into
openshift:mainfrom
Pratik-Redhat-Tech:doc-mirror-registry-lifecycle

Conversation

@Pratik-Redhat-Tech

@Pratik-Redhat-Tech Pratik-Redhat-Tech commented Sep 11, 2026

Copy link
Copy Markdown

Summary

  • Adds a Version support and lifecycle section to modules/mirror-registry-introduction.adoc
  • Documents that only the latest released version of the mirror registry for Red Hat OpenShift is supported
  • Links to the published life cycle policy for version dates and support phases

Addresses the documentation gap described in KCS 7083311: release notes exist but the product documentation did not explain the support period or lifecycle for each version.

Jira: https://redhat.atlassian.net/browse/OCPBUGS-122280

Test plan

  • Verify AsciiDoc renders correctly in the disconnected install / mirror registry documentation assembly
  • Confirm life cycle policy link resolves correctly

Add a section explaining that only the latest mirror registry version
is supported and link to the published life cycle policy page.

Co-authored-by: Cursor <cursoragent@cursor.com>
@openshift-ci openshift-ci Bot added size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Sep 11, 2026
@openshift-ci

openshift-ci Bot commented Sep 11, 2026

Copy link
Copy Markdown

Hi @Pratik-Redhat-Tech. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

@Pratik-Redhat-Tech Pratik-Redhat-Tech changed the title Document mirror registry version support and lifecycle policy OCPBUGS-122280: Document mirror registry version support and lifecycle policy Sep 11, 2026
@Pratik-Redhat-Tech

Copy link
Copy Markdown
Author

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Sep 11, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@Pratik-Redhat-Tech: This pull request references Jira Issue OCPBUGS-122280, which is invalid:

  • expected the bug to target the "5.1.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Summary

  • Adds a Version support and lifecycle section to modules/mirror-registry-introduction.adoc
  • Documents that only the latest released version of the mirror registry for Red Hat OpenShift is supported
  • Links to the published life cycle policy for version dates and support phases

Addresses the documentation gap described in KCS 7083311: release notes exist but the product documentation did not explain the support period or lifecycle for each version.

Jira: https://redhat.atlassian.net/browse/OCPBUGS-122280

Test plan

  • Verify AsciiDoc renders correctly in the disconnected install / mirror registry documentation assembly
  • Confirm life cycle policy link resolves correctly

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot

Copy link
Copy Markdown

@Pratik-Redhat-Tech: This pull request references Jira Issue OCPBUGS-122280, which is invalid:

  • expected the bug to target the "5.1.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

/jira refresh

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 openshift-eng/jira-lifecycle-plugin repository.

@Pratik-Redhat-Tech

Copy link
Copy Markdown
Author

/jira refresh

@openshift-ci-robot

Copy link
Copy Markdown

@Pratik-Redhat-Tech: This pull request references Jira Issue OCPBUGS-122280, which is invalid:

  • expected the bug to target the "5.1.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

/jira refresh

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 openshift-eng/jira-lifecycle-plugin repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. 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.

2 participants