Merge pull request #27770 from CaoDonghui123/fix7
[zh]Resync Tutorials (2)
This commit is contained in:
		
						commit
						83589d3ffb
					
				
										
											
												File diff suppressed because it is too large
												Load Diff
											
										
									
								
							| 
						 | 
				
			
			@ -100,16 +100,15 @@ The manifest file, included below, specifies a Deployment controller that runs a
 | 
			
		|||
1. 在下载清单文件的目录中启动终端窗口。
 | 
			
		||||
2. 从 `mongo-deployment.yaml` 文件中应用 MongoDB Deployment:
 | 
			
		||||
 | 
			
		||||
      <!---
 | 
			
		||||
      for local testing of the content via relative file path
 | 
			
		||||
      kubectl apply -f ./content/en/examples/application/guestbook/mongo-deployment.yaml
 | 
			
		||||
      -->
 | 
			
		||||
 | 
			
		||||
      ```shell
 | 
			
		||||
      kubectl apply -f https://k8s.io/examples/application/guestbook/mongo-deployment.yaml
 | 
			
		||||
      ```
 | 
			
		||||
 | 
			
		||||
<!---
 | 
			
		||||
for local testing of the content via relative file path
 | 
			
		||||
kubectl apply -f ./content/en/examples/application/guestbook/mongo-deployment.yaml
 | 
			
		||||
-->
 | 
			
		||||
 | 
			
		||||
 | 
			
		||||
<!--
 | 
			
		||||
1. Query the list of Pods to verify that the MongoDB Pod is running:
 | 
			
		||||
-->
 | 
			
		||||
| 
						 | 
				
			
			@ -156,15 +155,15 @@ The guestbook application needs to communicate to the MongoDB to write its data.
 | 
			
		|||
-->
 | 
			
		||||
1. 使用下面的 `mongo-service.yaml` 文件创建 MongoDB 的服务:
 | 
			
		||||
 | 
			
		||||
      <!---
 | 
			
		||||
      for local testing of the content via relative file path
 | 
			
		||||
      kubectl apply -f ./content/en/examples/application/guestbook/mongo-service.yaml
 | 
			
		||||
      -->
 | 
			
		||||
   
 | 
			
		||||
      ```shell
 | 
			
		||||
      kubectl apply -f https://k8s.io/examples/application/guestbook/mongo-service.yaml
 | 
			
		||||
      ```
 | 
			
		||||
 | 
			
		||||
<!---
 | 
			
		||||
for local testing of the content via relative file path
 | 
			
		||||
kubectl apply -f ./content/en/examples/application/guestbook/mongo-service.yaml
 | 
			
		||||
-->
 | 
			
		||||
 | 
			
		||||
<!--
 | 
			
		||||
1. Query the list of Services to verify that the MongoDB Service is running:
 | 
			
		||||
-->
 | 
			
		||||
| 
						 | 
				
			
			@ -182,7 +181,7 @@ kubectl apply -f ./content/en/examples/application/guestbook/mongo-service.yaml
 | 
			
		|||
      ```shell
 | 
			
		||||
      NAME           TYPE        CLUSTER-IP   EXTERNAL-IP   PORT(S)    AGE
 | 
			
		||||
      kubernetes     ClusterIP   10.0.0.1     <none>        443/TCP    1m
 | 
			
		||||
      mongo          ClusterIP   10.0.0.151   <none>        6379/TCP   8s
 | 
			
		||||
      mongo          ClusterIP   10.0.0.151   <none>        27017/TCP   8s
 | 
			
		||||
      ```
 | 
			
		||||
 | 
			
		||||
<!--
 | 
			
		||||
| 
						 | 
				
			
			@ -216,15 +215,15 @@ The guestbook application has a web frontend serving the HTTP requests written i
 | 
			
		|||
-->
 | 
			
		||||
1. 从 `frontend-deployment.yaml` 应用前端 Deployment 文件:
 | 
			
		||||
 | 
			
		||||
      <!---
 | 
			
		||||
      for local testing of the content via relative file path
 | 
			
		||||
      kubectl apply -f ./content/en/examples/application/guestbook/frontend-deployment.yaml
 | 
			
		||||
      -->
 | 
			
		||||
   
 | 
			
		||||
      ```shell
 | 
			
		||||
      kubectl apply -f https://k8s.io/examples/application/guestbook/frontend-deployment.yaml
 | 
			
		||||
      ```
 | 
			
		||||
 | 
			
		||||
<!---
 | 
			
		||||
for local testing of the content via relative file path
 | 
			
		||||
kubectl apply -f ./content/en/examples/application/guestbook/frontend-deployment.yaml
 | 
			
		||||
-->
 | 
			
		||||
 | 
			
		||||
<!--
 | 
			
		||||
1. Query the list of Pods to verify that the three frontend replicas are running:
 | 
			
		||||
-->
 | 
			
		||||
| 
						 | 
				
			
			@ -253,10 +252,11 @@ kubectl apply -f ./content/en/examples/application/guestbook/frontend-deployment
 | 
			
		|||
### 创建前端服务
 | 
			
		||||
 | 
			
		||||
<!--
 | 
			
		||||
The `mongo` Services you applied is only accessible within the Kubernetes cluster because the default type for a Service is [ClusterIP](/docs/concepts/services-networking/service/#publishing-services---service-types). `ClusterIP` provides a single IP address for the set of Pods the Service is pointing to. This IP address is accessible only within the cluster.
 | 
			
		||||
The `mongo` Services you applied is only accessible within the Kubernetes cluster because the default type for a Service is [ClusterIP](/docs/concepts/services-networking/service/#publishing-services-service-types). `ClusterIP` provides a single IP address for the set of Pods the Service is pointing to. This IP address is accessible only within the cluster.
 | 
			
		||||
-->
 | 
			
		||||
应用的 `mongo` 服务只能在 Kubernetes 集群中访问,因为服务的默认类型是
 | 
			
		||||
[ClusterIP](/zh/docs/concepts/services-networking/service/#publishing-services---service-types)。`ClusterIP` 为服务指向的 Pod 集提供一个 IP 地址。这个 IP 地址只能在集群中访问。
 | 
			
		||||
[ClusterIP](/zh/docs/concepts/services-networking/service/#publishing-services-service-types)。
 | 
			
		||||
`ClusterIP` 为服务指向的 Pod 集提供一个 IP 地址。这个 IP 地址只能在集群中访问。
 | 
			
		||||
 | 
			
		||||
<!--
 | 
			
		||||
If you want guests to be able to access your guestbook, you must configure the frontend Service to be externally visible, so a client can request the Service from outside the Kubernetes cluster. However a Kubernetes user you can use `kubectl port-forward` to access the service even though it uses a `ClusterIP`.
 | 
			
		||||
| 
						 | 
				
			
			@ -278,15 +278,15 @@ Some cloud providers, like Google Compute Engine or Google Kubernetes Engine, su
 | 
			
		|||
-->
 | 
			
		||||
1. 从 `frontend-service.yaml` 文件中应用前端服务:
 | 
			
		||||
 | 
			
		||||
      <!---
 | 
			
		||||
      for local testing of the content via relative file path
 | 
			
		||||
      kubectl apply -f ./content/en/examples/application/guestbook/frontend-service.yaml
 | 
			
		||||
      -->
 | 
			
		||||
   
 | 
			
		||||
      ```shell
 | 
			
		||||
      kubectl apply -f https://k8s.io/examples/application/guestbook/frontend-service.yaml
 | 
			
		||||
      ```
 | 
			
		||||
 | 
			
		||||
<!---
 | 
			
		||||
for local testing of the content via relative file path
 | 
			
		||||
kubectl apply -f ./content/en/examples/application/guestbook/frontend-service.yaml
 | 
			
		||||
-->
 | 
			
		||||
 | 
			
		||||
<!--
 | 
			
		||||
1. Query the list of Services to verify that the frontend Service is running:
 | 
			
		||||
-->
 | 
			
		||||
| 
						 | 
				
			
			@ -365,7 +365,7 @@ If you deployed the `frontend-service.yaml` manifest with type: `LoadBalancer` y
 | 
			
		|||
 | 
			
		||||
      ```
 | 
			
		||||
      NAME       TYPE           CLUSTER-IP      EXTERNAL-IP        PORT(S)        AGE
 | 
			
		||||
      frontend   ClusterIP   10.51.242.136   109.197.92.229     80:32372/TCP   1m
 | 
			
		||||
      frontend   LoadBalancer   10.51.242.136   109.197.92.229     80:32372/TCP   1m
 | 
			
		||||
      ```
 | 
			
		||||
 | 
			
		||||
<!--
 | 
			
		||||
| 
						 | 
				
			
			
 | 
			
		|||
		Loading…
	
		Reference in New Issue