[zh] Fix remove duplicate words
Signed-off-by: ydFu <ader.ydfu@gmail.com>pull/35994/head
ydFu
parent
762ede868a
commit
6e8e47ed9e
|
|
@ -15,6 +15,7 @@ namespace. These annotations apply to `Event` object from API group
|
|||
-->
|
||||
该页面作为 kubernetes.io 名字空间的审计注解的参考。这些注解适用于 API 组 `audit.k8s.io` 中的 `Event` 对象。
|
||||
|
||||
{{< note >}}
|
||||
<!--
|
||||
The following annotations are not used within the Kubernetes API. When you
|
||||
[enable auditing](/docs/tasks/debug/debug-cluster/audit/) in your cluster,
|
||||
|
|
@ -23,10 +24,10 @@ The annotations apply to audit events. Audit events are different from objects i
|
|||
[Event API](/docs/reference/kubernetes-api/cluster-resources/event-v1/) (API group
|
||||
`events.k8s.io`).
|
||||
-->
|
||||
{{< note >}}
|
||||
Kubernetes API 中不使用以下注解。当你在集群中[启用审计](/zh-cn/docs/tasks/debug/debug-cluster/audit/)时，
|
||||
审计事件数据将使用 API 组 `audit.k8s.io` 中的 `Event` 写入。
|
||||
注解适用于审计事件。审计事件不同于[事件 API ](/zh-cn/docs/reference/kubernetes-api/cluster-resources/event-v1/)
|
||||
注解适用于审计事件。
|
||||
审计事件不同于[事件 API](/zh-cn/docs/reference/kubernetes-api/cluster-resources/event-v1/)
|
||||
（API 组 `events.k8s.io`）中的对象。
|
||||
{{</note>}}
|
||||
|
||||
|
|
@ -135,7 +136,7 @@ See [Auditing](/docs/tasks/debug/debug-cluster/audit/) for more information.
|
|||
|
||||
有关详细信息，请参阅[审计](/zh-cn/docs/tasks/debug/debug-cluster/audit/)。
|
||||
|
||||
## missing-san.invalid-cert.kubernetes.io/$hostname
|
||||
## missing-san.invalid-cert.kubernetes.io/$hostname {##missing-san-invalid-cert-kubernetes-io-hostname}
|
||||
|
||||
<!--
|
||||
Example: `missing-san.invalid-cert.kubernetes.io/example-svc.example-namespace.svc: "relies on a legacy Common Name field instead of the SAN extension for subject validation"`
|
||||
|
|
@ -170,7 +171,7 @@ There's more information about this in the Go documentation:
|
|||
Go 文档中有更多关于此的信息：
|
||||
[X.509 CommonName 弃用](https://go.dev/doc/go1.15#commonname)。
|
||||
|
||||
## insecure-sha1.invalid-cert.kubernetes.io/$hostname
|
||||
## insecure-sha1.invalid-cert.kubernetes.io/$hostname {#insecure-sha1-invalid-cert-kubernetes-io-hostname}
|
||||
|
||||
<!--
|
||||
Example: `insecure-sha1.invalid-cert.kubernetes.io/example-svc.example-namespace.svc: "uses an insecure SHA-1 signature"`
|
||||
|
|
@ -187,7 +188,7 @@ is using an insecure certificate signed with a SHA-1 hash.
|
|||
Support for these insecure certificates is disabled by default in Kubernetes 1.24,
|
||||
and will be removed in a future release.
|
||||
-->
|
||||
此注解表示 webhook 或聚合 API 服务器正在使用使用 SHA-1 签名的不安全证书。
|
||||
此注解表示 webhook 或聚合 API 服务器所使用的是使用 SHA-1 签名的不安全证书。
|
||||
Kubernetes 1.24 已经默认禁用，并将在未来的版本中删除对这些证书的支持。
|
||||
|
||||
<!--
|
||||
|
|
|
|||
|
|
@ -17,7 +17,7 @@ weight: 50
|
|||
<!--
|
||||
This page shows how to use Weave Net for NetworkPolicy.
|
||||
-->
|
||||
本页展示如何使用使用 Weave Net 提供 NetworkPolicy。
|
||||
本页展示如何使用 Weave Net 提供 NetworkPolicy。
|
||||
|
||||
## {{% heading "prerequisites" %}}
|
||||
|
||||
|
|
@ -42,7 +42,7 @@ The Weave Net addon for Kubernetes comes with a
|
|||
that automatically monitors Kubernetes for any NetworkPolicy annotations on all
|
||||
namespaces and configures `iptables` rules to allow or block traffic as directed by the policies.
|
||||
-->
|
||||
## 安装 Weave Net 插件
|
||||
## 安装 Weave Net 插件 {#install-the-weave-net-addon}
|
||||
|
||||
按照[通过插件集成 Kubernetes](https://www.weave.works/docs/net/latest/kubernetes/kube-addon/)
|
||||
指南执行安装。
|
||||
|
|
@ -59,17 +59,19 @@ Verify that the weave works.
|
|||
|
||||
Enter the following command:
|
||||
-->
|
||||
## 测试安装
|
||||
## 测试安装 {#test-the-installation}
|
||||
|
||||
验证 weave 是否有效。
|
||||
|
||||
输入以下命令：
|
||||
|
||||
```shell
|
||||
kubectl get po -n kube-system -o wide
|
||||
kubectl get pods -n kube-system -o wide
|
||||
```
|
||||
|
||||
<!-- The output is similar to this: -->
|
||||
<!--
|
||||
The output is similar to this:
|
||||
-->
|
||||
输出类似这样：
|
||||
|
||||
```
|
||||
|
|
@ -83,13 +85,16 @@ weave-net-pmw8w 2/2 Running 0 9d
|
|||
<!--
|
||||
Each Node has a weave Pod, and all Pods are `Running` and `2/2 READY`. (`2/2` means that each Pod has `weave` and `weave-npc`.)
|
||||
-->
|
||||
每个 Node 都有一个 weave Pod，所有 Pod 都是`Running` 和 `2/2 READY`。
|
||||
（`2/2` 表示每个 Pod 都有 `weave` 和 `weave-npc`）
|
||||
每个 Node 都有一个 weave Pod，所有 Pod 都是 `Running` 和 `2/2 READY`。
|
||||
（`2/2` 表示每个 Pod 都有 `weave` 和 `weave-npc`。）
|
||||
|
||||
## {{% heading "whatsnext" %}}
|
||||
|
||||
<!--
|
||||
Once you have installed the Weave Net addon, you can follow the [Declare Network Policy](/docs/tasks/administer-cluster/declare-network-policy/) to try out Kubernetes NetworkPolicy. If you have any question, contact us at [#weave-community on Slack or Weave User Group](https://github.com/weaveworks/weave#getting-help).
|
||||
Once you have installed the Weave Net addon, you can follow the
|
||||
[Declare Network Policy](/docs/tasks/administer-cluster/declare-network-policy/)
|
||||
to try out Kubernetes NetworkPolicy. If you have any question, contact us at
|
||||
[#weave-community on Slack or Weave User Group](https://github.com/weaveworks/weave#getting-help).
|
||||
-->
|
||||
安装 Weave Net 插件后，你可以参考
|
||||
[声明网络策略](/zh-cn/docs/tasks/administer-cluster/declare-network-policy/)
|
||||
|
|
@ -97,4 +102,3 @@ Once you have installed the Weave Net addon, you can follow the [Declare Network
|
|||
如果你有任何疑问，请通过
|
||||
[Slack 上的 #weave-community 频道或者 Weave 用户组](https://github.com/weaveworks/weave#getting-help)
|
||||
联系我们。
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue