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
Refer to the documentation for your cluster deployment tool to learn the recommended set
@@ -132,7 +132,7 @@ up steps for maintenance.
132
132
133
133
### 切换集群的存储 API 版本 {#switch-your-clusters-storage-api-version}
134
134
135
-
<!--
135
+
<!--
136
136
The objects that are serialized into etcd for a cluster's internal
137
137
representation of the Kubernetes resources active in the cluster are
138
138
written using a particular version of the API.
@@ -152,7 +152,7 @@ write it back also using the latest supported API.
152
152
153
153
对于每个受影响的对象,请使用最新支持的 API 读取它,然后使用所支持的最新 API 将其写回。
154
154
155
-
<!--
155
+
<!--
156
156
### Update manifests
157
157
158
158
Upgrading to a new Kubernetes version can provide new APIs.
@@ -171,7 +171,7 @@ For example:
171
171
kubectl convert -f pod.yaml --output-version v1
172
172
```
173
173
174
-
<!--
174
+
<!--
175
175
The `kubectl` tool replaces the contents of `pod.yaml` with a manifest that sets `kind` to
176
176
Pod (unchanged), but with a revised `apiVersion`.
177
177
-->
@@ -187,13 +187,14 @@ release with a newer device plugin API version, device plugins must be upgraded
187
187
both version before the node is upgraded in order to guarantee that device allocations
188
188
continue to complete successfully during the upgrade.
189
189
190
-
Refer to [API compatiblity](docs/concepts/extend-kubernetes/compute-storage-net/device-plugins.md/#api-compatibility) and [Kubelet Device Manager API Versions](docs/reference/node/device-plugin-api-versions.md) for more details.
190
+
Refer to [API compatibility](/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins/#api-compatibility) and [Kubelet Device Manager API Versions](/docs/reference/node/device-plugin-api-versions/) for more details.
0 commit comments