Skip to content

Commit

Permalink
[zh-cn] sync service user-namespaces controller-manager-leader-migration
Browse files Browse the repository at this point in the history
Signed-off-by: xin.li <xin.li@daocloud.io>
  • Loading branch information
my-git9 committed Jun 11, 2023
1 parent 82d421d commit 4c69081
Show file tree
Hide file tree
Showing 3 changed files with 132 additions and 81 deletions.
4 changes: 2 additions & 2 deletions content/zh-cn/docs/concepts/services-networking/service.md
Original file line number Diff line number Diff line change
Expand Up @@ -2000,7 +2000,7 @@ for that Service.
When you define a Service, you can specify `externalIPs` for any
[service type](#publishing-services-service-types).
In the example below, the Service named `"my-service"` can be accessed by clients using TCP,
on `"198.51.100.32:80"` (calculated from `.spec.externalIP` and `.spec.port`).
on `"198.51.100.32:80"` (calculated from `.spec.externalIPs[]` and `.spec.ports[].port`).
-->
### 外部 IP {#external-ips}

Expand All @@ -2011,7 +2011,7 @@ on `"198.51.100.32:80"` (calculated from `.spec.externalIP` and `.spec.port`).
定义 Service 时,你可以为任何[服务类型](#publishing-services-service-types)指定 `externalIPs`

在下面的例子中,名为 `my-service` 的服务可以在 "`198.51.100.32:80`"
(从 .spec.externalIP 和 .spec.port 计算)上被客户端使用 TCP 协议访问。
(从 `.spec.externalIPs[]``.spec.ports[].port` 计算)上被客户端使用 TCP 协议访问。

```yaml
apiVersion: v1
Expand Down
4 changes: 2 additions & 2 deletions content/zh-cn/docs/concepts/workloads/pods/user-namespaces.md
Original file line number Diff line number Diff line change
Expand Up @@ -90,7 +90,7 @@ to use this feature with Kubernetes stateless pods:
* CRI-O: version 1.25 (and later) supports user namespaces for containers.
Please note that containerd v1.7 supports user namespaces for containers,
compatible with Kubernetes {{< skew currentVersion >}}. It should not be used
compatible with Kubernetes {{< skew currentPatchVersion >}}. It should not be used
with Kubernetes 1.27 (and later).
Support for this in [cri-dockerd is not planned][CRI-dockerd-issue] yet.
Expand All @@ -101,7 +101,7 @@ Support for this in [cri-dockerd is not planned][CRI-dockerd-issue] yet.

* CRI-O:1.25(及更高)版本支持配置容器的用户命名空间。

请注意,containerd v1.7 支持配置容器的用户命名空间,与 Kubernetes {{< skew currentVersion >}}
请注意,containerd v1.7 支持配置容器的用户命名空间,与 Kubernetes {{< skew currentPatchVersion >}}
兼容。它不应与 Kubernetes 1.27(及更高)版本一起使用。

目前 [cri-dockerd 没有计划][CRI-dockerd-issue]支持此功能。
Expand Down
Loading

0 comments on commit 4c69081

Please sign in to comment.