[zh] Tidy up and fix links in tasks section (4/10)
This commit is contained in:
@@ -4,11 +4,9 @@ content_type: task
|
||||
weight: 40
|
||||
---
|
||||
<!--
|
||||
---
|
||||
title: Imperative Management of Kubernetes Objects Using Configuration Files
|
||||
content_type: task
|
||||
weight: 40
|
||||
---
|
||||
-->
|
||||
|
||||
<!-- overview -->
|
||||
@@ -20,29 +18,24 @@ This document explains how to define and manage objects using configuration file
|
||||
可以使用 `kubectl` 命令行工具以及用 YAML 或 JSON 编写的对象配置文件来创建、更新和删除 Kubernetes 对象。
|
||||
本文档说明了如何使用配置文件定义和管理对象。
|
||||
|
||||
|
||||
## {{% heading "prerequisites" %}}
|
||||
|
||||
|
||||
<!--
|
||||
Install [`kubectl`](/docs/tasks/tools/install-kubectl/).
|
||||
-->
|
||||
安装 [`kubectl`](/docs/tasks/tools/install-kubectl/) 。
|
||||
安装 [`kubectl`](/zh/docs/tasks/tools/install-kubectl/) 。
|
||||
|
||||
{{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}
|
||||
|
||||
|
||||
|
||||
<!-- steps -->
|
||||
|
||||
<!--
|
||||
## Trade-offs
|
||||
|
||||
The `kubectl` tool supports three kinds of object management:
|
||||
-->
|
||||
## 权衡
|
||||
|
||||
<!--
|
||||
The `kubectl` tool supports three kinds of object management:
|
||||
-->
|
||||
`kubectl` 工具支持三种对象管理:
|
||||
|
||||
<!--
|
||||
@@ -58,30 +51,26 @@ The `kubectl` tool supports three kinds of object management:
|
||||
See [Kubernetes Object Management](/docs/concepts/overview/working-with-objects/object-management/)
|
||||
for a discussion of the advantages and disadvantage of each kind of object management.
|
||||
-->
|
||||
参看 [Kubernetes 对象管理](/docs/concepts/overview/working-with-objects/object-management/) 讨论每种对象管理的优缺点。
|
||||
参看 [Kubernetes 对象管理](/zh/docs/concepts/overview/working-with-objects/object-management/)
|
||||
中关于每种对象管理的优缺点的讨论。
|
||||
|
||||
<!--
|
||||
## How to create objects
|
||||
-->
|
||||
## 如何创建对象
|
||||
|
||||
<!--
|
||||
You can use `kubectl create -f` to create an object from a configuration file.
|
||||
Refer to the [kubernetes API reference](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/)
|
||||
for details.
|
||||
-->
|
||||
您可以使用 `kubectl create -f` 从配置文件创建一个对象。
|
||||
## 如何创建对象
|
||||
|
||||
你可以使用 `kubectl create -f` 从配置文件创建一个对象。
|
||||
请参考 [kubernetes API 参考](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/) 有关详细信息。
|
||||
|
||||
* `kubectl create -f <filename|url>`
|
||||
|
||||
<!--
|
||||
## How to update objects
|
||||
-->
|
||||
## 如何更新对象
|
||||
|
||||
{{< warning >}}
|
||||
<!--
|
||||
Updating objects with the `replace` command drops all
|
||||
parts of the spec not specified in the configuration file. This
|
||||
should not be used with objects whose specs are partially managed
|
||||
@@ -90,8 +79,12 @@ the `externalIPs` field is managed independently from the configuration
|
||||
file. Independently managed fields must be copied to the configuration
|
||||
file to prevent `replace` from dropping them.
|
||||
-->
|
||||
## 如何更新对象
|
||||
|
||||
{{< warning >}}
|
||||
使用 `replace` 命令更新对象会删除所有未在配置文件中指定的规范的某些部分。
|
||||
不应将其规范由集群部分管理的对象使用,比如类型为 `LoadBalancer` 的服务,其中 `externalIPs` 字段独立于配置文件进行管理。
|
||||
不应将其规范由集群部分管理的对象使用,比如类型为 `LoadBalancer` 的服务,
|
||||
其中 `externalIPs` 字段独立于配置文件进行管理。
|
||||
必须将独立管理的字段复制到配置文件中,以防止 `replace` 删除它们。
|
||||
{{< /warning >}}
|
||||
|
||||
@@ -99,33 +92,31 @@ file to prevent `replace` from dropping them.
|
||||
You can use `kubectl replace -f` to update a live object according to a
|
||||
configuration file.
|
||||
-->
|
||||
您可以使用 `kubectl replace -f` 根据配置文件更新活动对象。
|
||||
你可以使用 `kubectl replace -f` 根据配置文件更新活动对象。
|
||||
|
||||
* `kubectl replace -f <filename|url>`
|
||||
|
||||
<!--
|
||||
## How to delete objects
|
||||
-->
|
||||
## 如何删除对象
|
||||
|
||||
<!--
|
||||
You can use `kubectl delete -f` to delete an object that is described in a
|
||||
configuration file.
|
||||
-->
|
||||
您可以使用 `kubectl delete -f` 删除配置文件中描述的对象。
|
||||
## 如何删除对象
|
||||
|
||||
你可以使用 `kubectl delete -f` 删除配置文件中描述的对象。
|
||||
|
||||
* `kubectl delete -f <filename|url>`
|
||||
|
||||
<!--
|
||||
## How to view an object
|
||||
-->
|
||||
## 如何查看对象
|
||||
|
||||
<!--
|
||||
You can use `kubectl get -f` to view information about an object that is
|
||||
described in a configuration file.
|
||||
-->
|
||||
您可以使用 `kubectl get -f` 查看有关配置文件中描述的对象的信息。
|
||||
## 如何查看对象
|
||||
|
||||
你可以使用 `kubectl get -f` 查看有关配置文件中描述的对象的信息。
|
||||
|
||||
* `kubectl get -f <filename|url> -o yaml`
|
||||
|
||||
@@ -138,10 +129,7 @@ Use `kubectl get -h` to see a list of options.
|
||||
|
||||
<!--
|
||||
## Limitations
|
||||
-->
|
||||
## 局限性
|
||||
|
||||
<!--
|
||||
The `create`, `replace`, and `delete` commands work well when each object's
|
||||
configuration is fully defined and recorded in its configuration
|
||||
file. However when a live object is updated, and the updates are not merged
|
||||
@@ -150,6 +138,8 @@ is executed. This can happen if a controller, such as
|
||||
a HorizontalPodAutoscaler, makes updates directly to a live object. Here's
|
||||
an example:
|
||||
-->
|
||||
## 局限性
|
||||
|
||||
当完全定义每个对象的配置并将其记录在其配置文件中时,`create`、 `replace` 和`delete` 命令会很好的工作。
|
||||
但是,当更新一个活动对象,并且更新没有合并到其配置文件中时,下一次执行 `replace` 时,更新将丢失。
|
||||
如果控制器,例如 HorizontalPodAutoscaler ,直接对活动对象进行更新,则会发生这种情况。
|
||||
@@ -173,17 +163,16 @@ If you need to support multiple writers to the same object, you can use
|
||||
|
||||
<!--
|
||||
## Creating and editing an object from a URL without saving the configuration
|
||||
-->
|
||||
## 从 URL 创建和编辑对象而不保存配置
|
||||
|
||||
<!--
|
||||
Suppose you have the URL of an object configuration file. You can use
|
||||
`kubectl create --edit` to make changes to the configuration before the
|
||||
object is created. This is particularly useful for tutorials and tasks
|
||||
that point to a configuration file that could be modified by the reader.
|
||||
-->
|
||||
假设您具有对象配置文件的 URL。
|
||||
您可以在创建对象之前使用 `kubectl create --edit` 对配置进行更改。
|
||||
## 从 URL 创建和编辑对象而不保存配置
|
||||
|
||||
假设你具有对象配置文件的 URL。
|
||||
你可以在创建对象之前使用 `kubectl create --edit` 对配置进行更改。
|
||||
这对于指向可以由读者修改的配置文件的教程和任务特别有用。
|
||||
|
||||
```shell
|
||||
@@ -192,13 +181,12 @@ kubectl create -f <url> --edit
|
||||
|
||||
<!--
|
||||
## Migrating from imperative commands to imperative object configuration
|
||||
-->
|
||||
## 从命令式命令迁移到命令式对象配置
|
||||
|
||||
<!--
|
||||
Migrating from imperative commands to imperative object configuration involves
|
||||
several manual steps.
|
||||
-->
|
||||
## 从命令式命令迁移到命令式对象配置
|
||||
|
||||
从命令式命令迁移到命令式对象配置涉及几个手动步骤。
|
||||
|
||||
<!--
|
||||
@@ -206,33 +194,33 @@ several manual steps.
|
||||
-->
|
||||
1. 将活动对象导出到本地对象配置文件:
|
||||
|
||||
```shell
|
||||
kubectl get <kind>/<name> -o yaml > <kind>_<name>.yaml
|
||||
```
|
||||
```shell
|
||||
kubectl get <kind>/<name> -o yaml > <kind>_<name>.yaml
|
||||
```
|
||||
|
||||
<!--
|
||||
1. Manually remove the status field from the object configuration file.
|
||||
-->
|
||||
1. 从对象配置文件中手动删除状态字段。
|
||||
2. 从对象配置文件中手动删除状态字段。
|
||||
|
||||
<!--
|
||||
1. For subsequent object management, use `replace` exclusively.
|
||||
-->
|
||||
1. 对于后续的对象管理,只能使用 `replace` 。
|
||||
3. 对于后续的对象管理,只能使用 `replace` 。
|
||||
|
||||
```shell
|
||||
kubectl replace -f <kind>_<name>.yaml
|
||||
```
|
||||
```shell
|
||||
kubectl replace -f <kind>_<name>.yaml
|
||||
```
|
||||
|
||||
<!--
|
||||
## Defining controller selectors and PodTemplate labels
|
||||
-->
|
||||
## 定义控制器选择器和 PodTemplate 标签
|
||||
|
||||
{{< warning >}}
|
||||
<!--
|
||||
Updating selectors on controllers is strongly discouraged.
|
||||
-->
|
||||
{{< warning >}}
|
||||
不建议在控制器上更新选择器。
|
||||
{{< /warning >}}
|
||||
|
||||
@@ -242,9 +230,7 @@ used only by the controller selector with no other semantic meaning.
|
||||
-->
|
||||
推荐的方法是定义单个不变的 PodTemplate 标签,该标签仅由控制器选择器使用,而没有其他语义。
|
||||
|
||||
<!--
|
||||
Example label:
|
||||
-->
|
||||
<!-- Example label: -->
|
||||
标签示例:
|
||||
|
||||
```yaml
|
||||
@@ -257,21 +243,17 @@ template:
|
||||
controller-selector: "apps/v1/deployment/nginx"
|
||||
```
|
||||
|
||||
|
||||
|
||||
## {{% heading "whatsnext" %}}
|
||||
|
||||
|
||||
<!--
|
||||
* [Managing Kubernetes Objects Using Imperative Commands](/docs/tasks/manage-kubernetes-objects/imperative-command/)
|
||||
* [Managing Kubernetes Objects Using Object Configuration (Declarative)](/docs/tasks/manage-kubernetes-objects/declarative-config/)
|
||||
* [Kubectl Command Reference](/docs/reference/generated/kubectl/kubectl/)
|
||||
* [Kubernetes API Reference](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/)
|
||||
-->
|
||||
* [使用命令式命令管理 Kubernetes 对象](/docs/tasks/manage-kubernetes-objects/imperative-command/)
|
||||
* [使用对象配置管理 Kubernetes 对象 (声明式)](/docs/tasks/manage-kubernetes-objects/declarative-config/)
|
||||
* [Kubectl 命令参考](/docs/reference/generated/kubectl/kubectl/)
|
||||
* [使用命令式命令管理 Kubernetes 对象](/zh/docs/tasks/manage-kubernetes-objects/imperative-command/)
|
||||
* [使用对象配置管理 Kubernetes 对象 (声明式)](/zh/docs/tasks/manage-kubernetes-objects/declarative-config/)
|
||||
* [Kubectl 命令参考](/docs/reference/generated/kubectl/kubectl-commands/)
|
||||
* [Kubernetes API 参考](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/)
|
||||
|
||||
|
||||
|
||||
|
||||
Reference in New Issue
Block a user