Skip to content

TELCODOCS-2736 DITA migration cleanup for update-ocp-update-prep.adoc #111656

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
lcavalle wants to merge 1 commit into
base: main
Choose a base branch
from
Open

TELCODOCS-2736 DITA migration cleanup for update-ocp-update-prep.adoc #111656

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
10 changes: 5 additions & 5 deletions modules/update-applying-mcp-labels-to-nodes-before-the-update.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,16 +12,14 @@ With MCP groups, you can reboot groups of nodes independently from the rest of t

You use the MCP node labels to pause and unpause the set of nodes during the update process so that you can do the update and reboot at a time of your choosing.

[id="update-staggering-the-cluster-update_{context}"]
== Staggering the cluster update
*Staggering the cluster update*

Sometimes there are problems during the update.
Often the problem is related to hardware failure or nodes needing to be reset.
Using MCP node labels, you can update nodes in stages by pausing the update at critical moments, tracking paused and unpaused nodes as you proceed.
When a problem occurs, you use the nodes that are in an unpaused state to ensure that there are enough nodes running to keep all applications pods running.

[id="update-dividing-worker-nodes-into-mcp-groups_{context}"]
== Dividing worker nodes into MachineConfigPool groups
*Dividing worker nodes into MachineConfigPool groups*

How you divide worker nodes into MCPs can vary depending on how many nodes are in the cluster or how many nodes you assign to a node role.
By default, the two roles in a cluster are control plane and worker roles.
Expand Down Expand Up @@ -60,4 +58,6 @@ Allow the updated nodes to sit through a day to allow for verification of applic
The process and pace at which you unpause the MCP groups is determined by your applications and configuration.

If your pod can handle being scheduled across nodes in a cluster, you can unpause several MCP groups at a time and set the `MaxUnavailable` field in the MCP custom resource (CR) to as high as 50%. This allows up to half of the nodes in an MCP group to restart and get updated.
====
====

.Procedure
2 changes: 2 additions & 0 deletions modules/update-ensuring-the-host-firmware-is-compatible.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,3 +20,5 @@ For example, workloads with high throughput requirements can be negatively affec
You should thoroughly test new firmware updates to ensure that they work as expected with the current version of {product-title}.
For best results, test the latest firmware version with the target {product-title} update version.
====

.Procedure
10 changes: 5 additions & 5 deletions ...tion_configuration/day_2_core_cnf_clusters/updating/update-ocp-update-prep.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,11 @@ toc::[]
[role="_abstract"]
On bare-metal hardware, you often must update the firmware to take on important security fixes, take on new functionality, or maintain compatibility with the new release of {product-title}.

[id="update-environment-considerations_{context}"]
== Disconnected environment considerations

To update clusters in disconnected environments, you must update your offline image repository.

include::modules/update-ensuring-the-host-firmware-is-compatible.adoc[leveloffset=+1]

include::modules/update-ensuring-that-layered-products-are-compatible.adoc[leveloffset=+1]
Expand Down Expand Up @@ -42,11 +47,6 @@ include::modules/update-creating-mcp-groups-for-the-cluster.adoc[leveloffset=+2]

* xref:../../../post_installation_configuration/day_2_core_cnf_clusters/updating/update-cnf-update-prep.adoc#update-pod-anti-affinity_update-cnf-update-prep[Ensuring that pods do not run on the same cluster node]

[id="update-environment-considerations_{context}"]
== Disconnected environment considerations

To update clusters in disconnected environments, you must update your offline image repository.

[role="_additional-resources"]
.Additional resources

Expand Down