Skip to content

OSDOCS Obsolete package-based RHEL references should be removed #112225

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.

Sign up for GitHub

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
mburke5678 wants to merge 1 commit into
base: main
Choose a base branch
from
+2 −4
Open

OSDOCS Obsolete package-based RHEL references should be removed #112225

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion modules/mirror-registry-introduction.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ The following limitations apply to the _mirror registry for Red{nbsp}Hat OpenShi

* The _mirror registry for Red{nbsp}Hat OpenShift_ is not intended to be a substitute for a production deployment of {quay}.

* The _mirror registry for Red{nbsp}Hat OpenShift_ is only supported for hosting images that are required to install a disconnected {product-title} cluster, such as Release images or Red{nbsp}Hat Operator images. It uses local storage on your {op-system-base-full} machine, and storage supported by {op-system-base} is supported by the _mirror registry for Red{nbsp}Hat OpenShift_.
* The _mirror registry for Red{nbsp}Hat OpenShift_ is only supported for hosting images that are required to install a disconnected {product-title} cluster, such as Release images or Red{nbsp}Hat Operator images. It uses local storage on your machine, and storage supported by {op-system-base} is supported by the _mirror registry for Red{nbsp}Hat OpenShift_.
+
[NOTE]
====
Expand Down
2 changes: 1 addition & 1 deletion modules/update-canary-about.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -48,5 +48,5 @@ However, you must determine whether the available nodes in the remaining MCPs ca

[NOTE]
====
You can use this update process with all documented {product-title} update processes. However, the process does not work with {op-system-base-full} machines, which are updated using Ansible playbooks.
You can use this update process with all documented {product-title} update processes.
====
2 changes: 0 additions & 2 deletions modules/update-service-overview.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,8 +39,6 @@ During the update process, the Machine Config Operator (MCO) applies the new con
The default setting for `maxUnavailable` is `1` for all the machine config pools in {product-title}. It is recommended to not change this value and update one control plane node at a time. Do not change this value to `3` for the control plane pool.
====

If you use {op-system-base-full} machines as workers, the MCO does not update the kubelet because you must update the OpenShift API on the machines first.

With the specification for the new version applied to the old kubelet, the {op-system-base} machine cannot return to the `Ready` state. You cannot complete the update until the machines are available. However, the maximum number of unavailable nodes is set to ensure that normal cluster operations can continue with that number of machines out of service.

The OpenShift Update Service is composed of an Operator and one or more application instances.