Skip to content

Commit a5023a5

Browse files
authored
Merge pull request #42227 from EricPonvelle/fixing-build-issues-main
Build Fixes: Build fixes for main
2 parents b019937 + 515a987 commit a5023a5

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

modules/upgrade-49-acknowledgement.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@
88
[id="upgrade-49-acknowledgement_{context}"]
99
= Administrator acknowledgment when upgrading to OpenShift 4.9
1010

11-
{product-title} 4.9 uses Kubernetes 1.22, which removed a link:https://docs.openshift.com/container-platform/4.9/release_notes/ocp-4-9-release-notes.html#ocp-4-9-removed-kube-1-22-apis[significant number of deprecated `v1beta1` APIs].
11+
{product-title} 4.9 uses Kubernetes 1.22, which removed a significant number of deprecated `v1beta1` APIs.
1212

1313
{product-title} 4.8.14 introduced a requirement that an administrator must provide a manual acknowledgment before the cluster can be upgraded from {product-title} 4.8 to 4.9. This is to help prevent issues after upgrading to {product-title} 4.9, where APIs that have been removed are still in use by workloads, tools, or other components running on or interacting with the cluster. Administrators must evaluate their cluster for any APIs in use that will be removed and migrate the affected components to use the appropriate new API version. After this is done, the administrator can provide the administrator acknowledgment.
1414

upgrading/osd-upgrading-cluster-prepare.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ include::modules/osd-update-preparing-list.adoc[leveloffset=+1]
2525
There are several methods to help administrators identify where APIs that will be removed are in use. However, {product-title} cannot identify all instances, especially workloads that are idle or external tools that are used. It is the responsibility of the administrator to properly evaluate all workloads and other integrations for instances of removed APIs.
2626

2727
// Reviewing alerts to identify uses of removed APIs
28-
include::modules/osd-update-preparing-evaluate-alerts.adoc[leveloffset=+1]
28+
include::modules/osd-update-preparing-evaluate-alerts.adoc[leveloffset=+2]
2929

3030
// Using APIRequestCount to identify uses of removed APIs
3131
include::modules/osd-update-preparing-evaluate-apirequestcount.adoc[leveloffset=+2]

0 commit comments

Comments
 (0)