whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge pull request #26245 from ydFu/update-new-sysc-in-0126

Browse Source 
[zh] update Sync concepts pages for secret and ingress
This commit is contained in:
Kubernetes Prow Robot
2021-01-25 21:30:34 -08:00
committed by GitHub
parent 3fce814f67 c669471823
commit 9ade714aab
2 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/zh/docs/concepts/configuration/secret.md
+1 -1
View File
@@ -494,7 +494,7 @@ SSH 私钥自身无法建立 SSH 客户端与服务器端之间的可信连接
<!-- <!--
### TLS secrets ### TLS secrets
Kubernetes provides a builtin Secret type `kubernetes.io/tls` for to storing Kubernetes provides a builtin Secret type `kubernetes.io/tls` for storing
a certificate and its associated key that are typically used for TLS . This a certificate and its associated key that are typically used for TLS . This
data is primarily used with TLS termination of the Ingress resource, but may data is primarily used with TLS termination of the Ingress resource, but may
be used with other resources or directly by a workload. be used with other resources or directly by a workload.
content/zh/docs/concepts/services-networking/ingress.md
+2 -2
View File
@@ -651,12 +651,12 @@ Ingress 控制器 IP 地址的任何网络流量，而无需基于名称的虚
<!-- <!--
For example, the following Ingress routes traffic For example, the following Ingress routes traffic
requested for `first.bar.com` to `service1`, `second.foo.com` to `service2`, and any traffic requested for `first.bar.com` to `service1`, `second.bar.com` to `service2`, and any traffic
to the IP address without a hostname defined in request (that is, without a request header being to the IP address without a hostname defined in request (that is, without a request header being
presented) to `service3`. presented) to `service3`.
--> -->
例如，以下 Ingress 会将针对 `first.bar.com` 的请求流量路由到 `service1`， 例如，以下 Ingress 会将针对 `first.bar.com` 的请求流量路由到 `service1`，
将针对 `second.foo.com` 的请求流量路由到 `service2`， 将针对 `second.bar.com` 的请求流量路由到 `service2`，
而针对该 IP 地址的、没有在请求中定义主机名的请求流量会被路由（即，不提供请求标头） 而针对该 IP 地址的、没有在请求中定义主机名的请求流量会被路由（即，不提供请求标头）
到 `service3`。 到 `service3`。