Skip to content

OSDOCS-17075_l:CQA updates #116254

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

Merged
brendan-daly-red-hat merged 1 commit into from
Jul 24, 2026
Merged

OSDOCS-17075_l:CQA updates #116254

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/nw-ingress-gateway-api-manage-succession.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,7 +40,7 @@ Backup and restore can fail or result in data loss for any CRD fields that were
$ oc get crd | grep -F -e gateway.networking.k8s.io -e gateway.networking.x-k8s.io
----
+
.Example output
*Example output:*
+
[source,terminal]
----
Expand Down
3 changes: 3 additions & 0 deletions modules/update-preparing-evaluate-alerts.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,9 @@
[id="update-preparing-evaluate-alerts_{context}"]
= Reviewing alerts to identify uses of removed APIs

[role="_abstract"]
Before you update your cluster, review alerts that identify removed API usage so that you can migrate affected workloads and avoid disruptions after the update.

Two alerts fire when an API is in use that will be removed in the next release:

* `APIRemovedInNextReleaseInUse` - for APIs that will be removed in the next {product-title} release.
Expand Down
12 changes: 12 additions & 0 deletions modules/update-preparing-evaluate-cluster.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,12 @@
// Module included in the following assemblies:
//
// * updating/preparing_for_updates/updating-cluster-prepare.adoc

:_mod-docs-content-type: CONCEPT
[id="evaluating-cluster-removed-apis_{context}"]
= Evaluating your cluster for removed APIs

[role="_abstract"]
Before you update your cluster, evaluate your workloads and integrations for uses of removed APIs so that you can migrate them to supported API versions and avoid disruptions.

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.
6 changes: 2 additions & 4 deletions updating/preparing_for_updates/updating-cluster-prepare.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,10 +27,8 @@ Before you can update your {product-title} 4.19 cluster to 4.20, you must provid
// Removed Kubernetes APIs
include::modules/update-preparing-list.adoc[leveloffset=+2]

[id="evaluating-cluster-removed-apis"]
=== Evaluating your cluster for removed APIs

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.
// Evaluating your cluster for removed APIs
include::modules/update-preparing-evaluate-cluster.adoc[leveloffset=+2]

// Reviewing alerts to identify uses of removed APIs
include::modules/update-preparing-evaluate-alerts.adoc[leveloffset=+3]
Expand Down