zh-trans: update static-pod.md (#14824)
This commit is contained in:
wangyamei
committed by
Kubernetes Prow Robot
Kubernetes Prow Robot
parent
f4441522e1
commit
19d42170f7
@@ -1,26 +1,76 @@
|
||||
---
|
||||
approvers:
|
||||
reviewers:
|
||||
- jsafrane
|
||||
title: 静态 Pods
|
||||
content_template: templates/concept
|
||||
---
|
||||
<!--
|
||||
---
|
||||
reviewers:
|
||||
- jsafrane
|
||||
title: Static Pods
|
||||
content_template: templates/concept
|
||||
---
|
||||
--->
|
||||
|
||||
**如果你正在运行 Kubernetes 集群并且使用静态 pods 在每个节点上起一个 pod，那么最好使用 [DaemonSet](/cn/docs/concepts/workloads/controllers/daemonset/)!**
|
||||
{{% capture overview %}}
|
||||
|
||||
*静态 pods* 直接由特定节点上的 kubelet 进程来管理，不通过主控节点上的 API 服务器。静态 pod 不关联任何 replication controller，它由 kubelet 进程自己来监控，当 pod 崩溃时重启该 pod。对于静态 pod 没有健康检查。静态 pod 始终绑定在某一个 kubelet，并且始终运行在同一个节点上。
|
||||
<!--
|
||||
**If you are running clustered Kubernetes and are using static pods to run a pod on every node, you should probably be using a [DaemonSet](/docs/concepts/workloads/controllers/daemonset/)!**
|
||||
--->
|
||||
**如果你正在运行 Kubernetes 集群并且使用静态 pods 在每个节点上起一个 pod，那么
|
||||
最好使用 [DaemonSet](/docs/concepts/workloads/controllers/daemonset/)!**
|
||||
|
||||
Kubelet 自动为每一个静态 pod 在 Kubernetes 的 API 服务器上创建一个镜像 Pod(Mirror Pod)，因此可以在 API 服务器查询到该 pod，但是不被 API 服务器控制(例如不能删除)。
|
||||
<!--
|
||||
*Static pods* are managed directly by kubelet daemon on a specific node, without the API server observing it. It does not have an associated replication controller, and kubelet daemon itself watches it and restarts it when it crashes. There is no health check. Static pods are always bound to one kubelet daemon and always run on the same node with it.
|
||||
--->
|
||||
*静态 pods* 直接由特定节点上的 kubelet 进程来管理，不通过主控节点上的 API 服务
|
||||
器。静态 pod 不关联任何 replication controller，它由 kubelet 进程自己来监控，当 pod 崩溃时重启该 pod。对于静态 pod 没有健康检查。静态 pod 始终绑定在某一个 kubelet，并且始终运行在同一个节点上。
|
||||
|
||||
<!--
|
||||
Kubelet automatically tries to create a *mirror pod* on the Kubernetes API server for each static pod.
|
||||
This means that the pods are visible on the API server but cannot be controlled from there.
|
||||
--->
|
||||
Kubelet 自动为每一个静态 pod 在 Kubernetes 的 API 服务器上创建一个 *镜像 Pod* (*mirror pod*)，因此可以在 API 服务器查询到该 pod，但是不被 API 服务器控制(例如不能删除)。
|
||||
|
||||
{{% /capture %}}
|
||||
|
||||
|
||||
{{% capture body %}}
|
||||
|
||||
<!--
|
||||
## Static pod creation
|
||||
|
||||
Static pod can be created in two ways: either by using configuration file(s) or by HTTP.
|
||||
--->
|
||||
## 静态 pod 创建
|
||||
|
||||
静态 pod 有两种创建方式：用配置文件或者通过 HTTP。
|
||||
|
||||
<!--
|
||||
### Configuration files
|
||||
|
||||
The configuration files are just standard pod definitions in json or yaml format in a specific directory. Use `kubelet --pod-manifest-path=<the directory>` to start kubelet daemon or add the `staticPodPath: <the directory>` field in the [KubeletConfiguration file](/docs/tasks/administer-cluster/kubelet-config-file), which periodically scans the directory and creates/deletes static pods as yaml/json files appear/disappear there.
|
||||
Note that kubelet will ignore files starting with dots when scanning the specified directory.
|
||||
--->
|
||||
### 配置文件
|
||||
|
||||
配置文件就是放在特定目录下的标准的 JSON 或 YAML 格式的 pod 定义文件。用`kubelet --pod-manifest-path=<the directory>`来启动 kubelet 进程，kubelet 将会周期扫描<the directory>这个目录，根据这个目录下出现或消失的 YAML/JSON 文件来创建或删除静态 pod。
|
||||
配置文件就是放在特定目录下的标准的 JSON 或 YAML 格式的 pod 定义文件。用 `kubelet --pod-manifest-path=<the directory>` 来启动 kubelet 进程或者在 [KubeletConfiguration 文件](/docs/tasks/administer-cluster/kubelet-config-file)中添加 `staticPodPath: <the directory>` 字段，kubelet 将会周期扫描 `<the directory>` 这个目录，根据这个目录下出现或消失的 YAML/JSON 文件来创建或删除静态 pod。
|
||||
|
||||
下面例子用静态 pod 的方式启动一个 nginx 的 Web 服务器：
|
||||
<!--
|
||||
For example, this is how to start a simple web server as a static pod:
|
||||
|
||||
1. 选择一个节点来运行静态 pod。这个例子中就是`my-node1`。
|
||||
1. Choose a node where we want to run the static pod. In this example, it's `my-node1`.
|
||||
|
||||
```
|
||||
[joe@host ~] $ ssh my-node1
|
||||
```
|
||||
|
||||
2. Choose a directory, say `/etc/kubelet.d` and place a web server pod definition there, e.g. `/etc/kubelet.d/static-web.yaml`:
|
||||
--->
|
||||
下面例子用静态 pod 的方式启动一个简单的 web 服务器：
|
||||
|
||||
1. 选择一个节点来运行静态 pod。这个例子中就是 `my-node1`。
|
||||
|
||||
```
|
||||
[joe@host ~] $ ssh my-node1
|
||||
@@ -48,27 +98,50 @@ Kubelet 自动为每一个静态 pod 在 Kubernetes 的 API 服务器上创建
|
||||
EOF
|
||||
```
|
||||
|
||||
3.配置节点上的 kubelet 使用这个目录，kubelet 启动时增加`--pod-manifest-path=/etc/kubelet.d/`参数。如果是 Fedora 系统，在 Kubelet 配置文件 /etc/kubernetes/kubelet 中添加下面这行：
|
||||
|
||||
<!--
|
||||
3. Configure your kubelet daemon on the node to use this directory by running it with `--pod-manifest-path=/etc/kubelet.d/` argument or add the `staticPodPath: <the directory>` field in the [KubeletConfiguration file](/docs/tasks/administer-cluster/kubelet-config-file).
|
||||
On Fedora edit `/etc/kubernetes/kubelet` to include this line:
|
||||
|
||||
```
|
||||
KUBELET_ARGS="--cluster-dns=10.254.0.10 --cluster-domain=kube.local --pod-manifest-path=/etc/kubelet.d/"
|
||||
```
|
||||
|
||||
Instructions for other distributions or Kubernetes installations may vary.
|
||||
--->
|
||||
3.配置节点上的 kubelet 使用这个目录，kubelet 启动时增加 `--pod-manifest-path=/etc/kubelet.d/` 参数或者在 [KubeletConfiguration 文件](/docs/tasks/administer-cluster/kubelet-config-file)中增加 `staticPodPath: <the directory>` 字段。如果是 Fedora 系统，在 Kubelet 配置文件 /etc/kubernetes/kubelet 中添加下面这行配置代码：
|
||||
|
||||
```
|
||||
KUBELET_ARGS="--cluster-dns=10.254.0.10 --cluster-domain=kube.local --pod-manifest-path=/etc/kubelet.d/"
|
||||
```
|
||||
|
||||
如果是其它 Linux 发行版或者其它 Kubernetes 安装方式，配置方法可能会不一样。
|
||||
|
||||
<!--
|
||||
4. Restart kubelet. On Fedora, this is:
|
||||
--->
|
||||
4. 重启 kubelet。如果是 Fedora 系统，就是：
|
||||
|
||||
```
|
||||
[root@my-node1 ~] $ systemctl restart kubelet
|
||||
```
|
||||
<!--
|
||||
### Pods created via HTTP
|
||||
|
||||
Kubelet periodically downloads a file specified by `--manifest-url=<URL>` argument and interprets it as a json/yaml file with a pod definition. It works the same as `--pod-manifest-path=<directory>`, i.e. it's reloaded every now and then and changes are applied to running static pods (see below).
|
||||
--->
|
||||
## 通过 HTTP 创建静态 Pods
|
||||
|
||||
Kubelet 周期地从 --manifest-url=<URL> 参数指定的地址下载文件，并且把它翻译成 JSON/YAML 格式的 pod 定义。此后的操作方式与 --pod-manifest-path=<directory> 相同，kubelet 会不时地重新下载该文件，当文件变化时对应地终止或启动静态 pod(如下)。
|
||||
|
||||
## 静态 pods 的动作行为
|
||||
<!--
|
||||
## Behavior of static pods
|
||||
|
||||
kubelet 启动时，由 `--pod-manifest-path=` 或者 `--manifest-url=` 参数指定的目录下定义的所有 pod 都会自动创建，例如，我们示例中的 static-web。 (可能要花些时间拉取 nginx 镜像，耐心等待...)
|
||||
When kubelet starts, it automatically starts all pods defined in directory specified in `--pod-manifest-path=` or `--manifest-url=` arguments or add the `staticPodPath: <the directory>` field in the [KubeletConfiguration file](/docs/tasks/administer-cluster/kubelet-config-file), i.e. our static-web. (It may take some time to pull nginx image, be patient…):
|
||||
--->
|
||||
## 静态 pods 的行为
|
||||
|
||||
kubelet 启动时，`--pod-manifest-path=` 或者 `--manifest-url=` 或者[KubeletConfiguration 文件](/docs/tasks/administer-cluster/kubelet-config-file)中的`staticPodPath: <the directory>` 参数指定的目录下定义的所有 pod 都会自动创建，例如，我们示例中的 static-web。 (可能要花些时
|
||||
间拉取 nginx 镜像，耐心等待...)
|
||||
|
||||
```shell
|
||||
[joe@my-node1 ~] $ docker ps
|
||||
@@ -76,6 +149,9 @@ CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAME
|
||||
f6d05272b57e nginx:latest "nginx" 8 minutes ago Up 8 minutes k8s_web.6f802af4_static-web-fk-node1_default_67e24ed9466ba55986d120c867395f3c_378e5f3c
|
||||
```
|
||||
|
||||
<!--
|
||||
If we look at our Kubernetes API server (running on host `my-master`), we see that a new mirror-pod was created there too:
|
||||
--->
|
||||
如果我们查看 Kubernetes 的 API 服务器(运行在主机 `my-master`)，可以看到这里创建了一个新的镜像 Pod：
|
||||
|
||||
```shell
|
||||
@@ -85,19 +161,35 @@ NAME READY STATUS RESTARTS AGE
|
||||
static-web-my-node1 1/1 Running 0 2m
|
||||
```
|
||||
|
||||
<!--
|
||||
Labels from the static pod are propagated into the mirror-pod and can be used as usual for filtering.
|
||||
|
||||
Notice we cannot delete the pod with the API server (e.g. via [`kubectl`](/docs/user-guide/kubectl/) command), kubelet simply won't remove it.
|
||||
--->
|
||||
静态 pod 的标签会传递给镜像 Pod，可以用来过滤或筛选。
|
||||
|
||||
需要注意的是，我们不能通过 API 服务器来删除静态 pod(例如，通过 [`kubectl`](/docs/user-guide/kubectl/) 命令)，kebelet 不会删除它。
|
||||
|
||||
<!--
|
||||
{{< note >}}
|
||||
Make sure the kubelet has permission to create the mirror pod in the API server. If not, the creation request is rejected by the API server. See
|
||||
[PodSecurityPolicy](/docs/concepts/policy/pod-security-policy/).
|
||||
{{< /note >}}
|
||||
--->
|
||||
{{< note >}}
|
||||
需要确保 kubelet 有权限在 API 服务器上创建镜像 pod。如果没有权限，API 服务器会拒绝创建请求，请参考 [PodSecurityPolicy](/docs/concepts/policy/pod-security-policy/)。
|
||||
{{< /note >}}
|
||||
```shell
|
||||
[joe@my-master ~] $ kubectl delete pod static-web-my-node1
|
||||
pods/static-web-my-node1
|
||||
pod "static-web-my-node1" deleted
|
||||
[joe@my-master ~] $ kubectl get pods
|
||||
NAME READY STATUS RESTARTS AGE
|
||||
static-web-my-node1 1/1 Running 0 12s
|
||||
```
|
||||
|
||||
返回`my-node1`主机，我们尝试手动终止容器，可以看到 kubelet 很快就会自动重启容器。
|
||||
<!--
|
||||
Back to our `my-node1` host, we can try to stop the container manually and see, that kubelet automatically restarts it in a while:
|
||||
--->
|
||||
返回 `my-node1` 主机，我们尝试手动终止容器，可以看到 kubelet 很快就会自动重启容器。
|
||||
|
||||
```shell
|
||||
[joe@host ~] $ ssh my-node1
|
||||
@@ -108,6 +200,11 @@ CONTAINER ID IMAGE COMMAND CREATED ...
|
||||
5b920cbaf8b1 nginx:latest "nginx -g 'daemon of 2 seconds ago ...
|
||||
```
|
||||
|
||||
<!--
|
||||
## Dynamic addition and removal of static pods
|
||||
|
||||
Running kubelet periodically scans the configured directory (`/etc/kubelet.d` in our example) for changes and adds/removes pods as files appear/disappear in this directory.
|
||||
--->
|
||||
## 静态 pods 的动态增加和删除
|
||||
|
||||
运行中的 kubelet 周期扫描配置的目录(我们这个例子中就是`/etc/kubelet.d`)下文件的变化，当这个目录中有文件出现或消失时创建或删除 pods。
|
||||
@@ -123,3 +220,5 @@ CONTAINER ID IMAGE COMMAND CREATED ...
|
||||
CONTAINER ID IMAGE COMMAND CREATED ...
|
||||
e7a62e3427f1 nginx:latest "nginx -g 'daemon of 27 seconds ago
|
||||
```
|
||||
|
||||
{{% /capture %}}
|
||||
|
||||
Reference in New Issue
Block a user