Merge pull request #39676 from Zhuzhenghao/service-access-application-cluster

[zh] resync page in tasks/access-application-cluster

Author: k8s-ci-robot

content/zh-cn/docs/tasks/access-application-cluster/connecting-frontend-backend.md

@@ -148,7 +148,7 @@ First, explore the Service configuration file:
 {{< codenew file="service/access/backend-service.yaml" >}}
 
 <!--
-In the configuration file, you can see that the Service named `hello` routes
+In the configuration file, you can see that the Service, named `hello` routes
 traffic to Pods that have the labels `app: hello` and `tier: backend`.
 -->
 配置文件中，你可以看到名为 `hello` 的 Service 将流量路由到包含 `app: hello`
@@ -182,8 +182,8 @@ given to the backend Service. The DNS name is `hello`, which is the value
 of the `name` field in the `examples/service/access/backend-service.yaml` 
 configuration file.
 
-The Pods in the frontend Deployment run an nginx image that is configured
-to proxy requests to the hello backend Service. Here is the nginx configuration file:
+The Pods in the frontend Deployment run a nginx image that is configured
+to proxy requests to the `hello` backend Service. Here is the nginx configuration file:
 -->
 ### 创建前端应用
 
@@ -195,7 +195,7 @@ to proxy requests to the hello backend Service. Here is the nginx configuration
 文件中 `name` 字段的取值。
 
 前端 Deployment 中的 Pods 运行一个 nginx 镜像，这个已经配置好的镜像会将请求转发
-给后端的 hello Service。下面是  nginx 的配置文件：
+给后端的 `hello` Service。下面是  nginx 的配置文件：
 
 {{< codenew file="service/access/frontend-nginx.conf" >}}
 
@@ -235,14 +235,14 @@ deployment.apps/frontend created
 service/frontend created
 ```
 
+{{< note >}}
 <!--
 The nginx configuration is baked into the
 [container image](/examples/service/access/Dockerfile). A better way to do this would
 be to use a
 [ConfigMap](/docs/tasks/configure-pod-container/configure-pod-configmap/),
 so that you can change the configuration more easily.
 -->
-{{< note >}}
 这个 nginx 配置文件是被打包在
 [容器镜像](/examples/service/access/Dockerfile) 里的。
 更好的方法是使用
@@ -261,7 +261,7 @@ command to find the external IP:
 一旦你创建了 LoadBalancer 类型的 Service，你可以使用这条命令查看外部 IP：
 
 ```shell
-kubectl get service frontend
+kubectl get service frontend --watch
 ```
 
 <!--
@@ -271,8 +271,8 @@ changes. Initially, the external IP is listed as `<pending>`:
 外部 IP 字段的生成可能需要一些时间。如果是这种情况，外部 IP 会显示为 `<pending>`。
 
 ```
-NAME       CLUSTER-IP      EXTERNAL-IP   PORT(S)  AGE
-frontend   10.51.252.116   <pending>     80/TCP   10s
+NAME       TYPE           CLUSTER-IP      EXTERNAL-IP   PORT(S)  AGE
+frontend   LoadBalancer   10.51.252.116   <pending>     80/TCP   10s
 ```
 
 <!--
@@ -282,8 +282,8 @@ to include the new IP under the `EXTERNAL-IP` heading:
 当外部 IP 地址被分配可用时，配置会更新，在 `EXTERNAL-IP` 头部下显示新的 IP：
 
 ```
-NAME       CLUSTER-IP      EXTERNAL-IP        PORT(S)  AGE
-frontend   10.51.252.116   XXX.XXX.XXX.XXX    80/TCP   1m
+NAME       TYPE           CLUSTER-IP      EXTERNAL-IP        PORT(S)  AGE
+frontend   LoadBalancer   10.51.252.116   XXX.XXX.XXX.XXX    80/TCP   1m
 ```
 
 <!--
@@ -336,6 +336,7 @@ To delete the Deployments, the ReplicaSets and the Pods that are running the bac
 ```shell
 kubectl delete deployment frontend backend
 ```
+
 ## {{% heading "whatsnext" %}}
 
 <!--
@@ -346,4 +347,3 @@ kubectl delete deployment frontend backend
 * 进一步了解 [Service](/zh-cn/docs/concepts/services-networking/service/)
 * 进一步了解 [ConfigMap](/zh-cn/docs/tasks/configure-pod-container/configure-pod-configmap/)
 * 进一步了解 [Service 和 Pods 的 DNS](/zh-cn/docs/concepts/services-networking/dns-pod-service/)
-

content/zh-cn/docs/tasks/access-application-cluster/create-external-load-balancer.md

@@ -160,10 +160,10 @@ The load balancer's IP address is listed next to `LoadBalancer Ingress`.
 -->
 负载均衡器的 IP 地址列在 `LoadBalancer Ingress` 旁边。
 
+{{< note >}}
 <!--
 If you are running your service on Minikube, you can find the assigned IP address and port with:
 -->
-{{< note >}}
 如果你在 Minikube 上运行服务，你可以通过以下命令找到分配的 IP 地址和端口：
 
 ```bash
@@ -264,7 +264,7 @@ Internal pod to pod traffic should behave similar to ClusterIP services, with eq
 内部 Pod 到 Pod 的流量应该与 ClusterIP 服务类似，所有 Pod 的概率相同。
 
 <!--
-## Garbage Collecting Load Balancers
+## Garbage collecting load balancers
 -->
 ## 回收负载均衡器   {#garbage-collecting-load-balancers}
 

content/zh-cn/docs/tasks/access-application-cluster/ingress-minikube.md

@@ -1,7 +1,7 @@
 ---
 title: 在 Minikube 环境中使用 NGINX Ingress 控制器配置 Ingress
 content_type: task
-weight: 100
+weight: 110
 min-kubernetes-server-version: 1.19
 ---
 <!--
@@ -49,7 +49,7 @@ Locally
 : If you already [installed Minikube](/docs/tasks/tools/#minikube)
   locally, run `minikube start` to create a cluster.
 -->
-### 创建一个 Minikube  集群  {#create-minikube-cluster}
+### 创建一个 Minikube 集群  {#create-minikube-cluster}
 
 使用 Katacoda
 : {{< kat-button >}}
@@ -201,7 +201,7 @@ Locally
    ```
 
 <!--
-1. Visit the service via NodePort:
+1. Visit the Service via NodePort:
 -->
 4. 使用节点端口信息访问服务：
 
@@ -327,7 +327,7 @@ The following manifest defines an Ingress that sends traffic to your Service via
    Ingress 列表中显示的 IP 地址会是内部 IP 地址。
    {{< /note >}}
 
-   <!--     
+   <!--
    After you make this change, your web browser sends requests for
    `hello-world.info` URLs to Minikube.
    -->
@@ -439,7 +439,7 @@ The following manifest defines an Ingress that sends traffic to your Service via
    ```
 
 <!--
-## Test Your Ingress
+## Test your Ingress
 
 1. Access the 1st version of the Hello World app.
 -->

content/zh-cn/docs/tasks/access-application-cluster/service-access-application-cluster.md

@@ -73,7 +73,7 @@ Here is the configuration file for the application Deployment:
    和一个关联的 {{< glossary_tooltip term_id="replica-set" text="ReplicaSet" >}} 对象。
    这个 ReplicaSet 有两个 {{< glossary_tooltip text="Pod" term_id="pod" >}}，
    每个 Pod 都运行着 Hello World 应用。
-  
+
 <!--
 1. Display information about the Deployment:
 -->
@@ -117,7 +117,7 @@ Here is the configuration file for the application Deployment:
    -->
    输出类似于：
 
-   ```
+   ```none
    Name:                   example-service
    Namespace:              default
    Labels:                 run=load-balancer-example
@@ -154,11 +154,12 @@ Here is the configuration file for the application Deployment:
 
    输出类似于：
 
-   ```
+   ```none
    NAME                           READY   STATUS    ...  IP           NODE
    hello-world-2895499144-bsbk5   1/1     Running   ...  10.200.1.4   worker1
    hello-world-2895499144-m1pwt   1/1     Running   ...  10.200.2.5   worker2
    ```
+
 <!--
 1. Get the public IP address of one of your nodes that is running
    a Hello World pod. How you get this address depends on how you set
@@ -198,7 +199,7 @@ Here is the configuration file for the application Deployment:
    这里的 `<public-node-ip>` 是你节点的公共 IP 地址，`<node-port>` 是你服务的 NodePort 值。
    对于请求成功的响应是一个 hello 消息：
 
-   ```shell
+   ```none
    Hello Kubernetes!
    ```
 
@@ -243,4 +244,3 @@ Follow the
 tutorial.
 -->
 跟随教程[使用 Service 连接到应用](/zh-cn/docs/tutorials/services/connect-applications-service/)。
-