You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: modules/update-preparing-list.adoc
+13-8Lines changed: 13 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,16 +5,21 @@
5
5
[id="update-preparing-list_{context}"]
6
6
= Removed Kubernetes APIs
7
7
8
-
{product-title} 4.15 uses Kubernetes 1.27, 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-27[Kubernetes documentation].
8
+
{product-title} 4.16 uses Kubernetes 1.29, 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-29[Kubernetes documentation].
9
9
10
-
.APIs removed from Kubernetes 1.27
11
-
[cols="2,2,2",options="header",]
10
+
.APIs removed from Kubernetes 1.29
11
+
[cols="2,2,2,1",options="header",]
12
12
|===
13
-
|Resource |Removed API |Migrate to
13
+
|Resource |Removed API |Migrate to |Notable changes
14
14
15
-
|`CSIStorageCapacity`
16
-
|`storage.k8s.io/v1beta1`
17
-
|`storage.k8s.io/v1`
15
+
|`FlowSchema`
16
+
|`flowcontrol.apiserver.k8s.io/v1beta2`
17
+
|`flowcontrol.apiserver.k8s.io/v1` or `flowcontrol.apiserver.k8s.io/v1beta3`
18
+
|No
19
+
20
+
|`PriorityLevelConfiguration`
21
+
|`flowcontrol.apiserver.k8s.io/v1beta2`
22
+
|`flowcontrol.apiserver.k8s.io/v1` or `flowcontrol.apiserver.k8s.io/v1beta3`
// Removed the "Notable changes" column since they were all "No" and table so wide it was causing a scrollbar. Add it back in for the next time there are notable changes (1.29)
Copy file name to clipboardExpand all lines: modules/update-preparing-migrate.adoc
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,4 +5,4 @@
5
5
[id="update-preparing-migrate_{context}"]
6
6
= Migrating instances of removed APIs
7
7
8
-
For information about how to migrate removed Kubernetes APIs, see the link:https://kubernetes.io/docs/reference/using-api/deprecation-guide/#v1-27[Deprecated API Migration Guide] in the Kubernetes documentation.
8
+
For information about how to migrate removed Kubernetes APIs, see the link:https://kubernetes.io/docs/reference/using-api/deprecation-guide/#v1-29[Deprecated API Migration Guide] in the Kubernetes documentation.
Copy file name to clipboardExpand all lines: updating/preparing_for_updates/updating-cluster-prepare.adoc
+4-9Lines changed: 4 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
:_mod-docs-content-type: ASSEMBLY
2
2
[id="updating-cluster-prepare"]
3
-
= Preparing to update to {product-title} 4.15
3
+
= Preparing to update to {product-title} 4.16
4
4
include::_attributes/common-attributes.adoc[]
5
5
:context: updating-cluster-prepare
6
6
@@ -27,15 +27,11 @@ Without the correct micro-architecture requirements, the update process will fai
27
27
[id="kube-api-removals_{context}"]
28
28
== Kubernetes API removals
29
29
30
-
There are no Kubernetes API removals in {product-title} 4.15.
30
+
{product-title} 4.16 uses Kubernetes 1.29, which removed several deprecated APIs.
31
31
32
-
// Commenting out this section because there are no APIs being removed in OCP 4.15 / Kube 1.28. But we'll need this section again for 4.16
33
-
////
34
-
{product-title} 4.14 uses Kubernetes 1.27, which removed several deprecated APIs.
35
-
36
-
A cluster administrator must provide a manual acknowledgment before the cluster can be updated from {product-title} 4.13 to 4.14. This is to help prevent issues after upgrading to {product-title} 4.14, 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.
32
+
A cluster administrator must provide a manual acknowledgment before the cluster can be updated from {product-title} 4.15 to 4.16. This is to help prevent issues after upgrading to {product-title} 4.16, 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.
37
33
38
-
Before you can update your {product-title} 4.13 cluster to 4.14, you must provide the administrator acknowledgment.
34
+
Before you can update your {product-title} 4.15 cluster to 4.16, you must provide the administrator acknowledgment.
Copy file name to clipboardExpand all lines: updating/updating_a_cluster/updating-cluster-cli.adoc
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,7 +30,7 @@ See xref:../../authentication/using-rbac.adoc#using-rbac[Using RBAC to define an
30
30
* Ensure that all machine config pools (MCPs) are running and not paused. Nodes associated with a paused MCP are skipped during the update process. You can pause the MCPs if you are performing a canary rollout update strategy.
31
31
* If your cluster uses manually maintained credentials, update the cloud provider resources for the new release. For more information, including how to determine if this is a requirement for your cluster, see xref:../../updating/preparing_for_updates/preparing-manual-creds-update.adoc#preparing-manual-creds-update[Preparing to update a cluster with manually maintained credentials].
32
32
* Ensure that you address all `Upgradeable=False` conditions so the cluster allows an update to the next minor version. An alert displays at the top of the *Cluster Settings* page when you have one or more cluster Operators that cannot be updated. You can still update to the next available patch update for the minor release you are currently on.
33
-
// * Review the list of APIs that were removed in Kubernetes 1.28, migrate any affected components to use the new API version, and provide the administrator acknowledgment. For more information, see xref:../../updating/preparing_for_updates/updating-cluster-prepare.adoc#updating-cluster-prepare[Preparing to update to {product-title} 4.14].
33
+
* Review the list of APIs that were removed in Kubernetes 1.28, migrate any affected components to use the new API version, and provide the administrator acknowledgment. For more information, see xref:../../updating/preparing_for_updates/updating-cluster-prepare.adoc#updating-cluster-prepare[Preparing to update to {product-title} 4.16].
34
34
* If you run an Operator or you have configured any application with the pod disruption budget, you might experience an interruption during the update process. If `minAvailable` is set to 1 in `PodDisruptionBudget`, the nodes are drained to apply pending machine configs which might block the eviction process. If several nodes are rebooted, all the pods might run on only one node, and the `PodDisruptionBudget` field can prevent the node drain.
0 commit comments