Skip to content

Commit 39d3ddd

Browse files
committed
[zh] Sync guestbook.md and overview.md
1 parent 3296a1d commit 39d3ddd

File tree

2 files changed

+21
-23
lines changed

2 files changed

+21
-23
lines changed

content/zh-cn/docs/concepts/configuration/overview.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -296,11 +296,11 @@ for a comprehensive list.
296296
<!--
297297
- Use label selectors for `get` and `delete` operations instead of specific object names. See the
298298
sections on [label selectors](/docs/concepts/overview/working-with-objects/labels/#label-selectors)
299-
and [using labels effectively](/docs/concepts/cluster-administration/manage-deployment/#using-labels-effectively).
299+
and [using labels effectively](/docs/concepts/overview/working-with-objects/labels/#using-labels-effectively).
300300
-->
301301
- 使用标签选择器进行 `get``delete` 操作,而不是特定的对象名称。
302302
- 请参阅[标签选择器](/zh-cn/docs/concepts/overview/working-with-objects/labels/#label-selectors)
303-
[有效使用标签](/zh-cn/docs/concepts/cluster-administration/manage-deployment/#using-labels-effectively)部分。
303+
[有效使用标签](/zh-cn/docs/concepts/overview/working-with-objects/labels/#using-labels-effectively)部分。
304304

305305
<!--
306306
- Use `kubectl create deployment` and `kubectl expose` to quickly create single-container

content/zh-cn/docs/tutorials/stateless-application/guestbook.md

Lines changed: 19 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: "示例:使用 Redis 部署 PHP 留言板应用程序"
2+
title: "示例:使用 Redis 部署 PHP 留言板应用"
33
content_type: tutorial
44
weight: 20
55
card:
@@ -9,7 +9,6 @@ card:
99
min-kubernetes-server-version: v1.14
1010
source: https://cloud.google.com/kubernetes-engine/docs/tutorials/guestbook
1111
---
12-
1312
<!--
1413
title: "Example: Deploying PHP Guestbook application with Redis"
1514
reviewers:
@@ -34,7 +33,7 @@ ready)_, multi-tier web application using Kubernetes and
3433
components:
3534
-->
3635
本教程向你展示如何使用 Kubernetes 和 [Docker](https://www.docker.com/)
37-
构建和部署一个简单的 **(非面向生产的)** 多层 Web 应用程序。本例由以下组件组成:
36+
构建和部署一个简单的 **(非面向生产的)** 多层 Web 应用。本例由以下组件组成:
3837

3938
<!--
4039
* A single-instance [Redis](https://www.redis.io/) to store guestbook entries
@@ -73,7 +72,7 @@ components:
7372
<!--
7473
The guestbook application uses Redis to store its data.
7574
-->
76-
留言板应用程序使用 Redis 存储数据。
75+
留言板应用使用 Redis 存储数据。
7776

7877
<!--
7978
### Creating the Redis Deployment
@@ -85,7 +84,7 @@ The manifest file, included below, specifies a Deployment controller that runs a
8584
-->
8685
下面包含的清单文件指定了一个 Deployment 控制器,该控制器运行一个 Redis Pod 副本。
8786

88-
{{< code file="application/guestbook/redis-leader-deployment.yaml" >}}
87+
{{% code_sample file="application/guestbook/redis-leader-deployment.yaml" %}}
8988

9089
<!--
9190
1. Launch a terminal window in the directory you downloaded the manifest files.
@@ -142,16 +141,16 @@ You need to apply a [Service](/docs/concepts/services-networking/service/) to
142141
proxy the traffic to the Redis Pod. A Service defines a policy to access the
143142
Pods.
144143
-->
145-
留言板应用程序需要往 Redis 中写数据。因此,需要创建
144+
留言板应用需要往 Redis 中写数据。因此,需要创建
146145
[Service](/zh-cn/docs/concepts/services-networking/service/) 来转发 Redis Pod
147146
的流量。Service 定义了访问 Pod 的策略。
148147

149-
{{< code file="application/guestbook/redis-leader-service.yaml" >}}
148+
{{% code_sample file="application/guestbook/redis-leader-service.yaml" %}}
150149

151150
<!--
152151
1. Apply the Redis Service from the following `redis-leader-service.yaml` file:
153152
-->
154-
1. 使用下面的 `redis-leader-service.yaml` 文件创建 Redis的服务
153+
1. 使用下面的 `redis-leader-service.yaml` 文件创建 Redis 的服务
155154

156155
<!---
157156
for local testing of the content via relative file path
@@ -188,8 +187,8 @@ This manifest file creates a Service named `redis-leader` with a set of labels
188187
that match the labels previously defined, so the Service routes network
189188
traffic to the Redis Pod.
190189
-->
191-
这个清单文件创建了一个名为 `redis-leader` 的 Service,其中包含一组
192-
与前面定义的标签匹配的标签,因此服务将网络流量路由到 Redis Pod 上。
190+
这个清单文件创建了一个名为 `redis-leader` 的 Service,
191+
其中包含一组与前面定义的标签匹配的标签,因此服务将网络流量路由到 Redis Pod 上。
193192
{{< /note >}}
194193

195194
<!--
@@ -203,7 +202,7 @@ and meet traffic demands by adding a few Redis followers, or replicas.
203202
尽管 Redis 领导者只有一个 Pod,你可以通过添加若干 Redis 跟随者来将其配置为高可用状态,
204203
以满足流量需求。
205204

206-
{{< code file="application/guestbook/redis-follower-deployment.yaml" >}}
205+
{{% code_sample file="application/guestbook/redis-follower-deployment.yaml" %}}
207206

208207
<!--
209208
1. Apply the Redis Deployment from the following `redis-follower-deployment.yaml` file:
@@ -253,7 +252,7 @@ Guestbook 应用需要与 Redis 跟随者通信以读取数据。
253252
为了让 Redis 跟随者可被发现,你必须创建另一个
254253
[Service](/zh-cn/docs/concepts/services-networking/service/)
255254

256-
{{< code file="application/guestbook/redis-follower-service.yaml" >}}
255+
{{% code_sample file="application/guestbook/redis-follower-service.yaml" %}}
257256

258257
<!--
259258
1. Apply the Redis Service from the following `redis-follower-service.yaml` file:
@@ -301,7 +300,6 @@ traffic to the Redis Pod.
301300
Redis Pod 之上。
302301
{{< /note >}}
303302

304-
305303
<!--
306304
## Set up and Expose the Guestbook Frontend
307305
-->
@@ -321,16 +319,16 @@ jQuery-Ajax-based UX.
321319
接下来可以启动 Guestbook 的 Web 服务器了。
322320
与 Redis 跟随者类似,前端也是使用 Kubernetes Deployment 来部署的。
323321

324-
Guestbook 应用使用 PHP 前端。该前端被配置成与后端的 Redis 跟随者或者
325-
领导者服务通信,具体选择哪个服务取决于请求是读操作还是写操作。
322+
Guestbook 应用使用 PHP 前端。该前端被配置成与后端的 Redis
323+
跟随者或者领导者服务通信,具体选择哪个服务取决于请求是读操作还是写操作。
326324
前端对外暴露一个 JSON 接口,并提供基于 jQuery-Ajax 的用户体验。
327325

328326
<!--
329327
### Creating the Guestbook Frontend Deployment
330328
-->
331329
### 创建 Guestbook 前端 Deployment {#creating-the-guestbook-frontend-deployment}
332330

333-
{{< code file="application/guestbook/frontend-deployment.yaml" >}}
331+
{{% code_sample file="application/guestbook/frontend-deployment.yaml" %}}
334332

335333
<!--
336334
1. Apply the frontend Deployment from the `frontend-deployment.yaml` file:
@@ -401,12 +399,12 @@ Some cloud providers, like Google Compute Engine or Google Kubernetes Engine,
401399
support external load balancers. If your cloud provider supports load
402400
balancers and you want to use it, uncomment `type: LoadBalancer`.
403401
-->
404-
一些云提供商,如 Google Compute Engine 或 Google Kubernetes Engine
405-
支持外部负载均衡器。如果你的云提供商支持负载均衡器,并且你希望使用它,
402+
Google Compute Engine 或 Google Kubernetes Engine
403+
这些云平台支持外部负载均衡器。如果你的云平台支持负载均衡器,并且你希望使用它,
406404
只需取消注释 `type: LoadBalancer`
407405
{{< /note >}}
408406

409-
{{< code file="application/guestbook/frontend-service.yaml" >}}
407+
{{% code_sample file="application/guestbook/frontend-service.yaml" %}}
410408

411409
<!--
412410
1. Apply the frontend Service from the `frontend-service.yaml` file:
@@ -655,10 +653,10 @@ labels to delete multiple resources with one command.
655653
* Complete the [Kubernetes Basics](/docs/tutorials/kubernetes-basics/) Interactive Tutorials
656654
* Use Kubernetes to create a blog using [Persistent Volumes for MySQL and Wordpress](/docs/tutorials/stateful-application/mysql-wordpress-persistent-volume/#visit-your-new-wordpress-blog)
657655
* Read more about [connecting applications with services](/docs/tutorials/services/connect-applications-service/)
658-
* Read more about [Managing Resources](/docs/concepts/cluster-administration/manage-deployment/#using-labels-effectively)
656+
* Read more about [using labels effectively](/docs/concepts/overview/working-with-objects/labels/#using-labels-effectively)
659657
-->
660658
* 完成 [Kubernetes 基础](/zh-cn/docs/tutorials/kubernetes-basics/) 交互式教程
661659
* 使用 Kubernetes 创建一个博客,使用
662660
[MySQL 和 Wordpress 的持久卷](/zh-cn/docs/tutorials/stateful-application/mysql-wordpress-persistent-volume/#visit-your-new-wordpress-blog)
663661
* 进一步阅读[使用 Service 连接到应用](/zh-cn/docs/tutorials/services/connect-applications-service/)
664-
* 进一步阅读[管理资源](/zh-cn/docs/concepts/cluster-administration/manage-deployment/#using-labels-effectively)
662+
* 进一步阅读[有效使用标签](/zh-cn/docs/concepts/overview/working-with-objects/labels/#using-labels-effectively)

0 commit comments

Comments
 (0)