[zh] Resync concepts section (7)
This commit is contained in:
Qiming Teng
@@ -20,10 +20,12 @@ that runs temporarily in an existing {{< glossary_tooltip term_id="pod" >}} to
|
||||
accomplish user-initiated actions such as troubleshooting. You use ephemeral
|
||||
containers to inspect services rather than to build applications.
|
||||
-->
|
||||
本页面概述了临时容器：一种特殊的容器，该容器在现有 {{< glossary_tooltip text="Pod" term_id="pod" >}}
|
||||
本页面概述了临时容器：一种特殊的容器，该容器在现有
|
||||
{{< glossary_tooltip text="Pod" term_id="pod" >}}
|
||||
中临时运行，以便完成用户发起的操作，例如故障排查。
|
||||
你会使用临时容器来检查服务，而不是用它来构建应用程序。
|
||||
|
||||
{{< warning >}}
|
||||
<!--
|
||||
Ephemeral containers are in early alpha state and are not suitable for production
|
||||
clusters. You should expect the feature not to work in some situations, such as
|
||||
@@ -31,11 +33,10 @@ when targeting the namespaces of a container. In accordance with the [Kubernetes
|
||||
Deprecation Policy](/docs/reference/using-api/deprecation-policy/), this alpha
|
||||
feature could change significantly in the future or be removed entirely.
|
||||
-->
|
||||
{{< warning >}}
|
||||
临时容器处于早期的 alpha 阶段，不适用于生产环境集群。
|
||||
临时容器处于早期的 Alpha 阶段，不适用于生产环境集群。
|
||||
应该预料到临时容器在某些情况下不起作用，例如在定位容器的命名空间时。
|
||||
根据 [Kubernetes 弃用政策](/zh/docs/reference/using-api/deprecation-policy/)，
|
||||
此 alpha 功能将来可能发生重大变化或被完全删除。
|
||||
此 Alpha 功能将来可能发生重大变化或被完全删除。
|
||||
{{< /warning >}}
|
||||
|
||||
<!-- body -->
|
||||
@@ -49,7 +50,7 @@ replaceable, you cannot add a container to a Pod once it has been created.
|
||||
Instead, you usually delete and replace Pods in a controlled fashion using
|
||||
{{< glossary_tooltip text="deployments" term_id="deployment" >}}.
|
||||
-->
|
||||
## 了解临时容器
|
||||
## 了解临时容器 {#understanding-ephemeral-containers}
|
||||
|
||||
{{< glossary_tooltip text="Pod" term_id="pod" >}} 是 Kubernetes 应用程序的基本构建块。
|
||||
由于 Pod 是一次性且可替换的，因此一旦 Pod 创建，就无法将容器加入到 Pod 中。
|
||||
@@ -74,7 +75,7 @@ they are not appropriate for building applications. Ephemeral containers are
|
||||
described using the same `ContainerSpec` as regular containers, but many fields
|
||||
are incompatible and disallowed for ephemeral containers.
|
||||
-->
|
||||
### 什么是临时容器？
|
||||
### 什么是临时容器？ {#what-is-an-ephemeral-container}
|
||||
|
||||
临时容器与其他容器的不同之处在于，它们缺少对资源或执行的保证，并且永远不会自动重启，
|
||||
因此不适用于构建应用程序。
|
||||
@@ -89,9 +90,7 @@ are incompatible and disallowed for ephemeral containers.
|
||||
-->
|
||||
- 临时容器没有端口配置，因此像 `ports`，`livenessProbe`，`readinessProbe`
|
||||
这样的字段是不允许的。
|
||||
|
||||
- Pod 资源分配是不可变的，因此 `resources` 配置是不允许的。
|
||||
|
||||
- 有关允许字段的完整列表，请参见
|
||||
[EphemeralContainer 参考文档](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#ephemeralcontainer-v1-core)。
|
||||
|
||||
@@ -116,7 +115,7 @@ Ephemeral containers are useful for interactive troubleshooting when `kubectl
|
||||
exec` is insufficient because a container has crashed or a container image
|
||||
doesn't include debugging utilities.
|
||||
-->
|
||||
## 临时容器的用途
|
||||
## 临时容器的用途 {#uses-for-ephemeral-containers}
|
||||
|
||||
当由于容器崩溃或容器镜像不包含调试工具而导致 `kubectl exec` 无用时，
|
||||
临时容器对于交互式故障排查很有用。
|
||||
@@ -128,7 +127,7 @@ and exposure to bugs and vulnerabilities. Since distroless images do not include
|
||||
shell or any debugging utilities, it's difficult to troubleshoot distroless
|
||||
images using `kubectl exec` alone.
|
||||
-->
|
||||
尤其是，[distroless 镜像](https://github.com/GoogleContainerTools/distroless)
|
||||
尤其是，[Distroless 镜像](https://github.com/GoogleContainerTools/distroless)
|
||||
允许用户部署最小的容器镜像，从而减少攻击面并减少故障和漏洞的暴露。
|
||||
由于 distroless 镜像不包含 Shell 或任何的调试工具，因此很难单独使用
|
||||
`kubectl exec` 命令进行故障排查。
|
||||
@@ -138,19 +137,28 @@ When using ephemeral containers, it's helpful to enable [process namespace
|
||||
sharing](/docs/tasks/configure-pod-container/share-process-namespace/) so
|
||||
you can view processes in other containers.
|
||||
-->
|
||||
使用临时容器时，启用[进程名字空间共享](/zh/docs/tasks/configure-pod-container/share-process-namespace/)
|
||||
使用临时容器时，启用
|
||||
[进程名字空间共享](/zh/docs/tasks/configure-pod-container/share-process-namespace/)
|
||||
很有帮助，可以查看其他容器中的进程。
|
||||
|
||||
<!--
|
||||
### Examples
|
||||
See [Debugging with Ephemeral Debug Container](/docs/tasks/debug-application-cluster/debug-running-pod/#ephemeral-container)
|
||||
for examples of troubleshooting using ephemeral containers.
|
||||
-->
|
||||
关于如何使用临时容器来执行故障排查的例子，可参阅
|
||||
[使用临时调试容器来调试](/zh/docs/tasks/debug-application-cluster/debug-running-pod/#ephemeral-container)。
|
||||
|
||||
<!--
|
||||
## Ephemeral containers API
|
||||
-->
|
||||
### 临时容器 API {#ephemeral-containers-api}」
|
||||
|
||||
{{< note >}}
|
||||
<!--
|
||||
The examples in this section require the `EphemeralContainers` [feature
|
||||
gate](/docs/reference/command-line-tools-reference/feature-gates/) to be
|
||||
enabled, and Kubernetes client and server version v1.16 or later.
|
||||
-->
|
||||
### 示例
|
||||
|
||||
{{< note >}}
|
||||
本节中的示例要求启用 `EphemeralContainers`
|
||||
[特性门控](/zh/docs/reference/command-line-tools-reference/feature-gates/)，
|
||||
并且 kubernetes 客户端和服务端版本要求为 v1.16 或更高版本。
|
||||
@@ -180,7 +188,7 @@ the ephemeral container to add as an `EphemeralContainers` list:
|
||||
"apiVersion": "v1",
|
||||
"kind": "EphemeralContainers",
|
||||
"metadata": {
|
||||
"name": "example-pod"
|
||||
"name": "example-pod"
|
||||
},
|
||||
"ephemeralContainers": [{
|
||||
"command": [
|
||||
@@ -281,34 +289,3 @@ You can attach to the new ephemeral container using `kubectl attach`:
|
||||
kubectl attach -it example-pod -c debugger
|
||||
```
|
||||
|
||||
<!--
|
||||
If process namespace sharing is enabled, you can see processes from all the containers in that Pod.
|
||||
For example, after attaching, you run `ps` in the debugger container:
|
||||
-->
|
||||
如果启用了进程命名空间共享，则可以查看该 Pod 所有容器中的进程。
|
||||
例如，运行上述 `attach` 操作后，在调试器容器中运行 `ps` 操作：
|
||||
|
||||
```shell
|
||||
# 在 "debugger" 临时容器内中运行此 shell 命令
|
||||
ps auxww
|
||||
```
|
||||
|
||||
运行命令后，输出类似于：
|
||||
|
||||
```
|
||||
PID USER TIME COMMAND
|
||||
1 root 0:00 /pause
|
||||
6 root 0:00 nginx: master process nginx -g daemon off;
|
||||
11 101 0:00 nginx: worker process
|
||||
12 101 0:00 nginx: worker process
|
||||
13 101 0:00 nginx: worker process
|
||||
14 101 0:00 nginx: worker process
|
||||
15 101 0:00 nginx: worker process
|
||||
16 101 0:00 nginx: worker process
|
||||
17 101 0:00 nginx: worker process
|
||||
18 101 0:00 nginx: worker process
|
||||
19 root 0:00 /pause
|
||||
24 root 0:00 sh
|
||||
29 root 0:00 ps auxww
|
||||
```
|
||||
|
||||
|
||||
Reference in New Issue
Block a user