Skip to content

[enterprise-4.20] OSDOCS#14987: Noting Kube APIs removed (again) in OCP 4.20) #100277

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
merged 1 commit into from
Oct 9, 2025
Merged

[enterprise-4.20] OSDOCS#14987: Noting Kube APIs removed (again) in OCP 4.20) #100277

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
4 changes: 2 additions & 2 deletions _topic_maps/_topic_map.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -750,10 +750,10 @@ Topics:
- Name: Preparing to update a cluster
Dir: preparing_for_updates
Topics:
- Name: Preparing to update to OpenShift Container Platform 4.19
- Name: Preparing to update to OpenShift Container Platform 4.20
File: updating-cluster-prepare
Distros: openshift-enterprise
- Name: Preparing to update to OKD 4.19
- Name: Preparing to update to OKD 4.20
File: updating-cluster-prepare
Distros: openshift-origin
- Name: Preparing to update a cluster with manually maintained credentials
Expand Down
4 changes: 2 additions & 2 deletions modules/update-preparing-ack.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@
[id="update-preparing-ack_{context}"]
= Providing the administrator acknowledgment

After you have evaluated your cluster for any removed APIs and have migrated any removed APIs, you can acknowledge that your cluster is ready to upgrade from {product-title} 4.18 to 4.19.
After you have evaluated your cluster for any removed APIs and have migrated any removed APIs, you can acknowledge that your cluster is ready to upgrade from {product-title} 4.19 to 4.20.

[WARNING]
====
Expand All @@ -23,5 +23,5 @@ Be aware that all responsibility falls on the administrator to ensure that all u
+
[source,terminal]
----
$ oc -n openshift-config patch cm admin-acks --patch '{"data":{"ack-4.18-kube-1.32-api-removals-in-4.19":"true"}}' --type=merge
$ oc -n openshift-config patch cm admin-acks --patch '{"data":{"ack-4.19-admissionregistration-v1beta1-api-removals-in-4.20":"true"}}' --type=merge
----
4 changes: 2 additions & 2 deletions modules/update-preparing-evaluate-apirequestcount-workloads.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,14 +25,14 @@ For example:
+
[source,terminal]
----
$ oc get apirequestcounts flowschemas.v1beta3.flowcontrol.apiserver.k8s.io -o yaml
$ oc get apirequestcounts mutatingwebhookconfigurations.v1beta1.admissionregistration.k8s.io -o yaml
----
+
You can also use `-o jsonpath` to extract the `username` and `userAgent` values from an `APIRequestCount` resource:
+
[source,terminal]
----
$ oc get apirequestcounts flowschemas.v1beta3.flowcontrol.apiserver.k8s.io \
$ oc get apirequestcounts mutatingwebhookconfigurations.v1beta1.admissionregistration.k8s.io \
-o jsonpath='{range .status.currentHour..byUser[*]}{..byVerb[*].verb}{","}{.username}{","}{.userAgent}{"\n"}{end}' \
| sort -k 2 -t, -u | column -t -s, -NVERBS,USERNAME,USERAGENT
----
Expand Down
7 changes: 2 additions & 5 deletions modules/update-preparing-evaluate-apirequestcount.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,9 +26,7 @@ $ oc get apirequestcounts
----
NAME REMOVEDINRELEASE REQUESTSINCURRENTHOUR REQUESTSINLAST24H
...
flowschemas.v1beta3.flowcontrol.apiserver.k8s.io 1.32 0 3
...
prioritylevelconfigurations.v1beta3.flowcontrol.apiserver.k8s.io 1.32 0 1
mutatingwebhookconfigurations.v1beta1.admissionregistration.k8s.io 1.22 0 3
...
----
+
Expand All @@ -50,6 +48,5 @@ $ oc get apirequestcounts -o jsonpath='{range .items[?(@.status.removedInRelease
.Example output
[source,terminal]
----
1.32 flowschemas.v1beta3.flowcontrol.apiserver.k8s.io
1.32 prioritylevelconfigurations.v1beta3.flowcontrol.apiserver.k8s.io
1.22 mutatingwebhookconfigurations.v1beta1.admissionregistration.k8s.io
----
32 changes: 21 additions & 11 deletions modules/update-preparing-list.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,23 +3,33 @@
// * updating/preparing_for_updates/updating-cluster-prepare.adoc

[id="update-preparing-list_{context}"]
= Removed Kubernetes APIs
= Removed APIs

{product-title} 4.19 uses Kubernetes 1.32, which removed the following deprecated APIs. You must migrate manifests and API clients to use the appropriate API version. For more information about migrating removed APIs, see the link:https://kubernetes.io/docs/reference/using-api/deprecation-guide/#v1-32[Kubernetes documentation].
{product-title} 4.20 removed the following Kubernetes APIs. You must migrate manifests and API clients to use the appropriate API version. For more information about migrating removed APIs, see the link:https://kubernetes.io/docs/reference/using-api/deprecation-guide/[Kubernetes documentation].

.APIs removed from Kubernetes 1.32
.Kubernetes APIs removed from {product-title} 4.20
[cols="2,2,2,1",options="header",]
|===
|Resource |Removed API |Migrate to |Notable changes

|`FlowSchema`
|`flowcontrol.apiserver.k8s.io/v1beta3`
|`flowcontrol.apiserver.k8s.io/v1`
|No
|`MutatingWebhookConfiguration`
|`admissionregistration.k8s.io/v1beta1`
|`admissionregistration.k8s.io/v1`
|link:https://kubernetes.io/docs/reference/using-api/deprecation-guide/#webhook-resources-v122[Yes]

|`PriorityLevelConfiguration`
|`flowcontrol.apiserver.k8s.io/v1beta3`
|`flowcontrol.apiserver.k8s.io/v1`
|link:https://kubernetes.io/docs/reference/using-api/deprecation-guide/#flowcontrol-resources-v132[Yes]
|`ValidatingAdmissionPolicy`
|`admissionregistration.k8s.io/v1beta1`
|`admissionregistration.k8s.io/v1`
|link:https://kubernetes.io/docs/reference/using-api/deprecation-guide/#webhook-resources-v122[Yes]

|`ValidatingAdmissionPolicyBinding`
|`admissionregistration.k8s.io/v1beta1`
|`admissionregistration.k8s.io/v1`
|link:https://kubernetes.io/docs/reference/using-api/deprecation-guide/#webhook-resources-v122[Yes]

|`ValidatingWebhookConfiguration`
|`admissionregistration.k8s.io/v1beta1`
|`admissionregistration.k8s.io/v1`
|link:https://kubernetes.io/docs/reference/using-api/deprecation-guide/#webhook-resources-v122[Yes]

|===
2 changes: 1 addition & 1 deletion modules/update-preparing-migrate.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,4 +5,4 @@
[id="update-preparing-migrate_{context}"]
= Migrating instances of removed APIs

For information about how to migrate removed Kubernetes APIs, see the link:https://kubernetes.io/docs/reference/using-api/deprecation-guide/#v1-32[Deprecated API Migration Guide] in the Kubernetes documentation.
For information about how to migrate removed Kubernetes APIs, see the link:https://kubernetes.io/docs/reference/using-api/deprecation-guide/[Deprecated API Migration Guide] in the Kubernetes documentation.
8 changes: 4 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
@@ -1,6 +1,6 @@
:_mod-docs-content-type: ASSEMBLY
[id="updating-cluster-prepare"]
= Preparing to update to {product-title} 4.19
= Preparing to update to {product-title} 4.20
include::_attributes/common-attributes.adoc[]
:context: updating-cluster-prepare

Expand All @@ -17,11 +17,11 @@ Learn more about administrative tasks that cluster admins must perform to succes
[id="kube-api-removals_{context}"]
== Kubernetes API removals

{product-title} 4.19 uses Kubernetes 1.32, which removed several deprecated Kubernetes APIs.
In {product-title} 4.17, a previously removed Kubernetes API was inadvertently reintroduced. It has been removed again in {product-title} 4.20.

A cluster administrator must provide a manual acknowledgment before the cluster can be updated from {product-title} 4.18 to 4.19. This is to help prevent issues after upgrading to {product-title} 4.19, 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 evaluation and migration is complete, the administrator can provide the acknowledgment.
A cluster administrator must provide a manual acknowledgment before the cluster can be updated from {product-title} 4.19 to 4.20. This is to help prevent issues after upgrading to {product-title} 4.20, 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 evaluation and migration is complete, the administrator can provide the acknowledgment.

Before you can update your {product-title} 4.18 cluster to 4.19, you must provide the administrator acknowledgment.
Before you can update your {product-title} 4.19 cluster to 4.20, you must provide the administrator acknowledgment.

// Removed Kubernetes APIs
include::modules/update-preparing-list.adoc[leveloffset=+2]
Expand Down