@@ -311,7 +311,7 @@ delete`](/docs/reference/generated/kubectl/kubectl-commands#delete). Kubectl wi
311
311
for it to delete each pod before deleting the ReplicationController itself. If this kubectl
312
312
command is interrupted, it can be restarted.
313
313
314
- When using the REST API or Go client library, you need to do the steps explicitly (scale replicas to
314
+ When using the REST API or [ client library](/docs/reference/using-api/client-libraries) , you need to do the steps explicitly (scale replicas to
315
315
0, wait for pod deletions, then delete the ReplicationController).
316
316
-->
317
317
# # 使用 ReplicationController {#working-with-replicationcontrollers}
@@ -323,7 +323,7 @@ When using the REST API or Go client library, you need to do the steps explicitl
323
323
kubectl 将 ReplicationController 缩放为 0 并等待以便在删除 ReplicationController 本身之前删除每个 Pod。
324
324
如果这个 kubectl 命令被中断,可以重新启动它。
325
325
326
- 当使用 REST API 或 Go 客户端库时 ,你需要明确地执行这些步骤(缩放副本为 0、
326
+ 当使用 REST API 或[客户端库](/zh/docs/reference/using-api/client-libraries)时 ,你需要明确地执行这些步骤(缩放副本为 0、
327
327
等待 Pod 删除,之后删除 ReplicationController 资源)。
328
328
329
329
<!--
@@ -333,15 +333,15 @@ You can delete a ReplicationController without affecting any of its pods.
333
333
334
334
Using kubectl, specify the `--cascade=orphan` option to [`kubectl delete`](/docs/reference/generated/kubectl/kubectl-commands#delete).
335
335
336
- When using the REST API or Go client library, simply delete the ReplicationController object.
336
+ When using the REST API or [ client library](/docs/reference/using-api/client-libraries), you can delete the ReplicationController object.
337
337
-->
338
338
# ## 只删除 ReplicationController
339
339
340
340
你可以删除一个 ReplicationController 而不影响它的任何 Pod。
341
341
342
342
使用 kubectl,为 [`kubectl delete`](/docs/reference/generated/kubectl/kubectl-commands#delete) 指定 `--cascade=orphan` 选项。
343
343
344
- 当使用 REST API 或 Go 客户端库时 ,只需删除 ReplicationController 对象。
344
+ 当使用 REST API 或客户端库(/zh/docs/reference/using-api/client-libraries)时 ,只需删除 ReplicationController 对象。
345
345
346
346
<!--
347
347
Once the original is deleted, you can create a new ReplicationController to replace it. As long
0 commit comments