diff --git a/content/zh-cn/docs/concepts/services-networking/ingress.md b/content/zh-cn/docs/concepts/services-networking/ingress.md index 61cde64155..2ee41f688f 100644 --- a/content/zh-cn/docs/concepts/services-networking/ingress.md +++ b/content/zh-cn/docs/concepts/services-networking/ingress.md @@ -309,7 +309,7 @@ Ingress 中的每个路径都需要有对应的路径类型(Path Type)。未 If the last element of the path is a substring of the last element in request path, it is not a match (for example: `/foo/bar` - matches`/foo/bar/baz`, but does not match `/foo/barbaz`). + matches `/foo/bar/baz`, but does not match `/foo/barbaz`). --> * `ImplementationSpecific`:对于这种路径类型,匹配方法取决于 IngressClass。 具体实现可以将其作为单独的 `pathType` 处理或者与 `Prefix` 或 `Exact` 类型作相同处理。 @@ -767,8 +767,8 @@ Name-based virtual hosts support routing HTTP traffic to multiple host names at The following Ingress tells the backing load balancer to route requests based on the [Host header](https://tools.ietf.org/html/rfc7230#section-5.4). --> -以下 Ingress 让后台负载均衡器基于 [host 头部字段](https://tools.ietf.org/html/rfc7230#section-5.4) -来路由请求。 +以下 Ingress 让后台负载均衡器基于 +[host 头部字段](https://tools.ietf.org/html/rfc7230#section-5.4)来路由请求。 {{< codenew file="service/networking/name-virtual-host-ingress.yaml" >}} diff --git a/content/zh-cn/docs/reference/labels-annotations-taints/_index.md b/content/zh-cn/docs/reference/labels-annotations-taints/_index.md index 8d11ab3bdc..3748d199c3 100644 --- a/content/zh-cn/docs/reference/labels-annotations-taints/_index.md +++ b/content/zh-cn/docs/reference/labels-annotations-taints/_index.md @@ -1644,11 +1644,11 @@ kubeadm 为本地管理的 etcd Pod 设置的注解,用来跟踪 etcd 客户 ### kubeadm.kubernetes.io/kube-apiserver.advertise-address.endpoint {#kube-apiserver-advertise-address-endpoint} -例子:`kubeadm.kubernetes.io/kube-apiserver.advertise-address.endpoint: https//172.17.0.18:6443` +例子:`kubeadm.kubernetes.io/kube-apiserver.advertise-address.endpoint: https://172.17.0.18:6443` 用于:Pod