Switch language name 'zh' to 'zh-cn'
This is the first step to rename 'zh' to 'zh-cn'. There are several reasons why we rename the language name.
- The upstream docsy theme changed the language name, leading to many warnings during site build;
The side-effect is that the i18n strings are no longer working.
- We believe renaming the language is the right thing to do, because this move can make room for other variants of Chinese language, such as 'zh-tw', 'zh-sg' etc.
There would be several follow-ups to this PR, such as fixing the intra-site links, adding redirects etc.
We will lock up changes to zh/zh-cn pages for the moment, until this one gets in.
This PR is based on commit cdad0a7342.
This commit is contained in:
Qiming Teng
@@ -0,0 +1,225 @@
|
||||
---
|
||||
title: 声明网络策略
|
||||
min-kubernetes-server-version: v1.8
|
||||
content_type: task
|
||||
---
|
||||
<!--
|
||||
reviewers:
|
||||
- caseydavenport
|
||||
- danwinship
|
||||
title: Declare Network Policy
|
||||
min-kubernetes-server-version: v1.8
|
||||
content_type: task
|
||||
-->
|
||||
|
||||
<!-- overview -->
|
||||
|
||||
<!--
|
||||
This document helps you get started using the Kubernetes [NetworkPolicy API](/docs/concepts/services-networking/network-policies/) to declare network policies that govern how pods communicate with each other.
|
||||
-->
|
||||
本文可以帮助你开始使用 Kubernetes 的
|
||||
[NetworkPolicy API](/zh/docs/concepts/services-networking/network-policies/)
|
||||
声明网络策略去管理 Pod 之间的通信
|
||||
|
||||
{{% thirdparty-content %}}
|
||||
|
||||
## {{% heading "prerequisites" %}}
|
||||
|
||||
{{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}
|
||||
|
||||
<!--
|
||||
Make sure you've configured a network provider with network policy support. There are a number of network providers that support NetworkPolicy, including:
|
||||
|
||||
* [Antrea](/docs/tasks/administer-cluster/network-policy-provider/antrea-network-policy/)
|
||||
* [Calico](/docs/tasks/administer-cluster/network-policy-provider/calico-network-policy/)
|
||||
* [Cilium](/docs/tasks/administer-cluster/network-policy-provider/cilium-network-policy/)
|
||||
* [Kube-router](/docs/tasks/administer-cluster/network-policy-provider/kube-router-network-policy/)
|
||||
* [Romana](/docs/tasks/administer-cluster/network-policy-provider/romana-network-policy/)
|
||||
* [Weave Net](/docs/tasks/administer-cluster/network-policy-provider/weave-network-policy/)
|
||||
-->
|
||||
你首先需要有一个支持网络策略的 Kubernetes 集群。已经有许多支持 NetworkPolicy 的网络提供商，包括：
|
||||
|
||||
* [Antrea](/zh/docs/tasks/administer-cluster/network-policy-provider/antrea-network-policy/)
|
||||
* [Calico](/zh/docs/tasks/administer-cluster/network-policy-provider/calico-network-policy/)
|
||||
* [Cilium](/zh/docs/tasks/administer-cluster/network-policy-provider/cilium-network-policy/)
|
||||
* [Kube-router](/zh/docs/tasks/administer-cluster/network-policy-provider/kube-router-network-policy/)
|
||||
* [Romana](/zh/docs/tasks/administer-cluster/network-policy-provider/romana-network-policy/)
|
||||
* [Weave 网络](/zh/docs/tasks/administer-cluster/network-policy-provider/weave-network-policy/)
|
||||
|
||||
<!-- steps -->
|
||||
|
||||
<!--
|
||||
## Create an `nginx` deployment and expose it via a service
|
||||
|
||||
To see how Kubernetes network policy works, start off by creating an `nginx` Deployment.
|
||||
-->
|
||||
## 创建一个`nginx` Deployment 并且通过服务将其暴露
|
||||
|
||||
为了查看 Kubernetes 网络策略是怎样工作的，可以从创建一个`nginx` Deployment 并且通过服务将其暴露开始
|
||||
|
||||
```shell
|
||||
kubectl create deployment nginx --image=nginx
|
||||
```
|
||||
|
||||
```none
|
||||
deployment.apps/nginx created
|
||||
```
|
||||
|
||||
<!--
|
||||
Expose the Deployment through a Service called `nginx`.
|
||||
-->
|
||||
将此 Deployment 以名为 `nginx` 的 Service 暴露出来：
|
||||
|
||||
```shell
|
||||
kubectl expose deployment nginx --port=80
|
||||
```
|
||||
|
||||
```none
|
||||
service/nginx exposed
|
||||
```
|
||||
|
||||
<!--
|
||||
The above commands create a Deployment with an nginx Pod and expose the Deployment through a Service named `nginx`. The `nginx` Pod and Deployment are found in the `default` namespace.
|
||||
-->
|
||||
上述命令创建了一个带有一个 nginx 的 Deployment，并将之通过名为 `nginx` 的
|
||||
Service 暴露出来。名为 `nginx` 的 Pod 和 Deployment 都位于 `default`
|
||||
名字空间内。
|
||||
|
||||
```shell
|
||||
kubectl get svc,pod
|
||||
```
|
||||
```none
|
||||
NAME CLUSTER-IP EXTERNAL-IP PORT(S) AGE
|
||||
svc/kubernetes 10.100.0.1 <none> 443/TCP 46m
|
||||
svc/nginx 10.100.0.16 <none> 80/TCP 33s
|
||||
|
||||
NAME READY STATUS RESTARTS AGE
|
||||
po/nginx-701339712-e0qfq 1/1 Running 0 35s
|
||||
```
|
||||
|
||||
<!--
|
||||
## Test the service by accessing it from another Pod
|
||||
|
||||
You should be able to access the new `nginx` service from other Pods. To access the `nginx` Service from another Pod in the `default` namespace, start a busybox container:
|
||||
-->
|
||||
## 通过从 Pod 访问服务对其进行测试
|
||||
|
||||
你应该可以从其它的 Pod 访问这个新的 `nginx` 服务。
|
||||
要从 default 命名空间中的其它s Pod 来访问该服务。可以启动一个 busybox 容器：
|
||||
|
||||
```shell
|
||||
kubectl run busybox --rm -ti --image=busybox:1.28 /bin/sh
|
||||
```
|
||||
|
||||
<!--
|
||||
In your shell, run the following command:
|
||||
-->
|
||||
在你的 Shell 中，运行下面的命令：
|
||||
|
||||
```shell
|
||||
wget --spider --timeout=1 nginx
|
||||
```
|
||||
|
||||
```none
|
||||
Connecting to nginx (10.100.0.16:80)
|
||||
remote file exists
|
||||
```
|
||||
|
||||
<!--
|
||||
## Limit access to the `nginx` service
|
||||
|
||||
To limit the access to the `nginx` service so that only Pods with the label `access: true` can query it, create a NetworkPolicy object as follows:
|
||||
-->
|
||||
## 限制 `nginx` 服务的访问
|
||||
|
||||
如果想限制对 `nginx` 服务的访问，只让那些拥有标签 `access: true` 的 Pod 访问它，
|
||||
那么可以创建一个如下所示的 NetworkPolicy 对象：
|
||||
|
||||
{{< codenew file="service/networking/nginx-policy.yaml" >}}
|
||||
|
||||
<!--
|
||||
The name of a NetworkPolicy object must be a valid
|
||||
[DNS subdomain name](/docs/concepts/overview/working-with-objects/names#dns-subdomain-names).
|
||||
-->
|
||||
NetworkPolicy 对象的名称必须是一个合法的
|
||||
[DNS 子域名](/zh/docs/concepts/overview/working-with-objects/names#dns-subdomain-names).
|
||||
|
||||
<!--
|
||||
NetworkPolicy includes a `podSelector` which selects the grouping of Pods to which the policy applies. You can see this policy selects Pods with the label `app=nginx`. The label was automatically added to the Pod in the `nginx` Deployment. An empty `podSelector` selects all pods in the namespace.
|
||||
-->
|
||||
{{< note >}}
|
||||
NetworkPolicy 中包含选择策略所适用的 Pods 集合的 `podSelector`。
|
||||
你可以看到上面的策略选择的是带有标签 `app=nginx` 的 Pods。
|
||||
此标签是被自动添加到 `nginx` Deployment 中的 Pod 上的。
|
||||
如果 `podSelector` 为空，则意味着选择的是名字空间中的所有 Pods。
|
||||
{{< /note >}}
|
||||
|
||||
<!--
|
||||
## Assign the policy to the service
|
||||
|
||||
Use kubectl to create a NetworkPolicy from the above `nginx-policy.yaml` file:
|
||||
-->
|
||||
## 为服务指定策略
|
||||
|
||||
使用 kubectl 根据上面的 `nginx-policy.yaml` 文件创建一个 NetworkPolicy：
|
||||
|
||||
```shell
|
||||
kubectl apply -f https://k8s.io/examples/service/networking/nginx-policy.yaml
|
||||
```
|
||||
```none
|
||||
networkpolicy.networking.k8s.io/access-nginx created
|
||||
```
|
||||
|
||||
<!--
|
||||
## Test access to the service when access label is not defined
|
||||
|
||||
When you attempt to access the `nginx` Service from a Pod without the correct labels, the request times out:
|
||||
-->
|
||||
## 测试没有定义访问标签时访问服务
|
||||
|
||||
如果你尝试从没有设定正确标签的 Pod 中去访问 `nginx` 服务，请求将会超时：
|
||||
|
||||
```shell
|
||||
kubectl run busybox --rm -ti --image=busybox:1.28 -- /bin/sh
|
||||
```
|
||||
|
||||
<!--
|
||||
In your shell, run the command:
|
||||
-->
|
||||
在 Shell 中运行命令：
|
||||
|
||||
```shell
|
||||
wget --spider --timeout=1 nginx
|
||||
```
|
||||
|
||||
```none
|
||||
Connecting to nginx (10.100.0.16:80)
|
||||
wget: download timed out
|
||||
```
|
||||
|
||||
<!--
|
||||
## Define access label and test again
|
||||
|
||||
You can create a Pod with the correct labels to see that the request is allowed:
|
||||
-->
|
||||
## 定义访问标签后再次测试
|
||||
|
||||
创建一个拥有正确标签的 Pod，你将看到请求是被允许的：
|
||||
|
||||
```shell
|
||||
kubectl run busybox --rm -ti --labels="access=true" --image=busybox:1.28 -- /bin/sh
|
||||
```
|
||||
<!--
|
||||
In your shell, run the command:
|
||||
-->
|
||||
在 Shell 中运行命令：
|
||||
|
||||
```shell
|
||||
wget --spider --timeout=1 nginx
|
||||
```
|
||||
|
||||
```none
|
||||
Connecting to nginx (10.100.0.16:80)
|
||||
remote file exists
|
||||
```
|
||||
|
||||
Reference in New Issue
Block a user