Skip to content

[OSDOCS#17059]: CQA 2.0 disconeted update withot OSUS#115120

Open
rh-sgehlot wants to merge 1 commit into
openshift:mainfrom
rh-sgehlot:OSDOCS#17059_CQA_2.0_disconnected_update
Open

[OSDOCS#17059]: CQA 2.0 disconeted update withot OSUS#115120
rh-sgehlot wants to merge 1 commit into
openshift:mainfrom
rh-sgehlot:OSDOCS#17059_CQA_2.0_disconnected_update

Conversation

@rh-sgehlot

@rh-sgehlot rh-sgehlot commented Jul 10, 2026

Copy link
Copy Markdown

Version(s):
4.20 +

Issue:
https://redhat.atlassian.net/browse/OSDOCS-17059

Link to docs preview:
https://115120--ocpdocs-pr.netlify.app/openshift-enterprise/latest/disconnected/updating/disconnected-update.html

QE review:

  • QE has approved this change.
  • QE approval not required as no change to the content.

Additional information:

@openshift-ci openshift-ci Bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Jul 10, 2026
@rh-sgehlot rh-sgehlot force-pushed the OSDOCS#17059_CQA_2.0_disconnected_update branch from b64d9df to 584bb9e Compare July 10, 2026 18:13
@openshift-ci

openshift-ci Bot commented Jul 10, 2026

Copy link
Copy Markdown

@rh-sgehlot: 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.

@skopacz1 skopacz1 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Nicely done, here are some initial comments and I can take another look once these are addressed next week.

Comment on lines 5 to 10
endif::openshift-origin[]
ifdef::openshift-origin[]
[id="updating-disconnected-cluster"]
= Updating a cluster in a disconnected environment by using the CLI
endif::openshift-origin[]
include::_attributes/common-attributes.adoc[]

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

So on the DITA errors guide page the author line error talks more about spacing in between headings and the following content, maybe adding spaces here wherever applicable would suffice:

Suggested change
endif::openshift-origin[]
ifdef::openshift-origin[]
[id="updating-disconnected-cluster"]
= Updating a cluster in a disconnected environment by using the CLI
endif::openshift-origin[]
include::_attributes/common-attributes.adoc[]

Comment on lines +15 to +16
[role="_abstract"]
You can update a cluster in a disconnected environment without using the OpenShift Update Service by using the CLI.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Okay I didn't actually realize that on the call, this addition was your own. I would actually have two intros here, one for enterprise docs that talks about updates without OSUS, and one for OKD that doesn't mention OSUS and instead focuses on the CLI:

Suggested change
[role="_abstract"]
You can update a cluster in a disconnected environment without using the OpenShift Update Service by using the CLI.
ifndef::openshift-origin[]
[role="_abstract"]
You can update a cluster in a disconnected environment without using the OpenShift Update Service.
endif::openshift-origin[]
ifdef::openshift-origin[]
[role="_abstract"]
You can update a cluster in a disconnected environment by using the CLI.
endif::openshift-origin[]

.Additional resources
* xref:../../disconnected/updating/mirroring-image-repository.adoc#mirroring-ocp-image-repository[Mirroring {product-title} images]
* xref:../../authentication/using-rbac.adoc#using-rbac[Using RBAC to define and apply permissions]
* xref:../../backup_and_restore/control_plane_backup_and_restore/backing-up-etcd.adoc#backup-etcd[etcd backup]

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Suggested change
* xref:../../backup_and_restore/control_plane_backup_and_restore/backing-up-etcd.adoc#backup-etcd[etcd backup]
* xref:../../backup_and_restore/control_plane_backup_and_restore/backing-up-etcd.adoc#backup-etcd[Backing up etcd]

* You must provision a local container image registry with the container images for your update, as described in "Mirroring {product-title} images".
* You must have access to the cluster as a user with `admin` privileges.
See "Using RBAC to define and apply permissions".
* You must have a recent "etcd backup" in case your update fails and you must "restore your cluster to a previous state".

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Suggested change
* You must have a recent "etcd backup" in case your update fails and you must "restore your cluster to a previous state".
* You must have a recent etcd backup in case your update fails and you must restore your cluster to a previous state.
For more information, see "Backing up etcd" and "Restoring to a previous cluster state".

* xref:../../disconnected/updating/mirroring-image-repository.adoc#mirroring-ocp-image-repository[Mirroring {product-title} images]
* xref:../../authentication/using-rbac.adoc#using-rbac[Using RBAC to define and apply permissions]
* xref:../../backup_and_restore/control_plane_backup_and_restore/backing-up-etcd.adoc#backup-etcd[etcd backup]
* xref:../../backup_and_restore/control_plane_backup_and_restore/disaster_recovery/scenario-2-restoring-cluster-state.adoc#dr-restoring-cluster-state[restore your cluster to a previous state]

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Suggested change
* xref:../../backup_and_restore/control_plane_backup_and_restore/disaster_recovery/scenario-2-restoring-cluster-state.adoc#dr-restoring-cluster-state[restore your cluster to a previous state]
* xref:../../backup_and_restore/control_plane_backup_and_restore/disaster_recovery/scenario-2-restoring-cluster-state.adoc#dr-restoring-cluster-state[Restoring to a previous cluster state]

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

Labels

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.

3 participants