sync cluster-ip-allocation dns-pod-service ingress-controller service-traffic-policy
parent
eb1ead1185
commit
bdc59a0913
|
@ -242,7 +242,7 @@ pie showData
|
|||
<!--
|
||||
## {{% heading "whatsnext" %}}
|
||||
* Read about [Service External Traffic Policy](/docs/tasks/access-application-cluster/create-external-load-balancer/#preserving-the-client-source-ip)
|
||||
* Read about [Connecting Applications with Services](/docs/concepts/services-networking/connect-applications-service/)
|
||||
* Read about [Connecting Applications with Services](/docs/tutorials/services/connect-applications-service/)
|
||||
* Read about [Services](/docs/concepts/services-networking/service/)
|
||||
-->
|
||||
## {{% heading "whatsnext" %}}
|
||||
|
|
|
@ -498,7 +498,7 @@ Pod 的 DNS 配置可让用户对 Pod 的 DNS 设置进行更多控制。
|
|||
This property is optional. When specified, the provided list will be merged
|
||||
into the base search domain names generated from the chosen DNS policy.
|
||||
Duplicate domain names are removed.
|
||||
Kubernetes allows for at most 6 search domains.
|
||||
Kubernetes allows up to 32 search domains.
|
||||
- `options`: an optional list of objects where each object may have a `name`
|
||||
property (required) and a `value` property (optional). The contents in this
|
||||
property will be merged to the options generated from the specified DNS policy.
|
||||
|
@ -512,7 +512,7 @@ Pod 的 DNS 配置可让用户对 Pod 的 DNS 设置进行更多控制。
|
|||
|
||||
- `searches`:用于在 Pod 中查找主机名的 DNS 搜索域的列表。此属性是可选的。
|
||||
指定此属性时,所提供的列表将合并到根据所选 DNS 策略生成的基本搜索域名中。
|
||||
重复的域名将被删除。Kubernetes 最多允许 6 个搜索域。
|
||||
重复的域名将被删除。Kubernetes 最多允许 32 个搜索域。
|
||||
|
||||
- `options`:可选的对象列表,其中每个对象可能具有 `name` 属性(必需)和 `value` 属性(可选)。
|
||||
此属性中的内容将合并到从指定的 DNS 策略生成的选项。
|
||||
|
@ -523,7 +523,7 @@ The following is an example Pod with custom DNS settings:
|
|||
-->
|
||||
以下是具有自定义 DNS 设置的 Pod 示例:
|
||||
|
||||
{{% code file="service/networking/custom-dns.yaml" %}}
|
||||
{{% code_sample file="service/networking/custom-dns.yaml" %}}
|
||||
|
||||
<!--
|
||||
When the Pod above is created, the container `test` gets the following contents
|
||||
|
@ -562,7 +562,7 @@ options ndots:5
|
|||
-->
|
||||
## DNS 搜索域列表限制 {#dns-search-domain-list-limits}
|
||||
|
||||
{{< feature-state for_k8s_version="1.26" state="beta" >}}
|
||||
{{< feature-state for_k8s_version="1.28" state="stable" >}}
|
||||
|
||||
<!--
|
||||
Kubernetes itself does not limit the DNS Config until the length of the search
|
||||
|
|
|
@ -53,16 +53,12 @@ Kubernetes 作为一个项目,目前支持和维护
|
|||
|
||||
<!--
|
||||
* [AKS Application Gateway Ingress Controller](https://docs.microsoft.com/azure/application-gateway/tutorial-ingress-controller-add-on-existing?toc=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Faks%2Ftoc.json&bc=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fbread%2Ftoc.json) is an ingress controller that configures the [Azure Application Gateway](https://docs.microsoft.com/azure/application-gateway/overview).
|
||||
* [Ambassador](https://www.getambassador.io/) API Gateway is an [Envoy](https://www.envoyproxy.io)-based ingress
|
||||
controller.
|
||||
* [Apache APISIX ingress controller](https://github.com/apache/apisix-ingress-controller) is an [Apache APISIX](https://github.com/apache/apisix)-based ingress controller.
|
||||
* [Avi Kubernetes Operator](https://github.com/vmware/load-balancer-and-ingress-services-for-kubernetes) provides L4-L7 load-balancing using [VMware NSX Advanced Load Balancer](https://avinetworks.com/).
|
||||
-->
|
||||
* [AKS 应用程序网关 Ingress 控制器](https://docs.microsoft.com/zh-cn/azure/application-gateway/tutorial-ingress-controller-add-on-existing?toc=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Faks%2Ftoc.json&bc=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fbread%2Ftoc.json)
|
||||
是一个配置 [Azure 应用程序网关](https://docs.microsoft.com/zh-cn/azure/application-gateway/overview)
|
||||
的 Ingress 控制器。
|
||||
* [Ambassador](https://www.getambassador.io/) API 网关是一个基于
|
||||
[Envoy](https://www.envoyproxy.io) 的 Ingress 控制器。
|
||||
* [Apache APISIX Ingress 控制器](https://github.com/apache/apisix-ingress-controller)
|
||||
是一个基于 [Apache APISIX 网关](https://github.com/apache/apisix) 的 Ingress 控制器。
|
||||
* [Avi Kubernetes Operator](https://github.com/vmware/load-balancer-and-ingress-services-for-kubernetes)
|
||||
|
@ -74,6 +70,8 @@ Kubernetes 作为一个项目,目前支持和维护
|
|||
* The [Citrix ingress controller](https://github.com/citrix/citrix-k8s-ingress-controller#readme) works with
|
||||
Citrix Application Delivery Controller.
|
||||
* [Contour](https://projectcontour.io/) is an [Envoy](https://www.envoyproxy.io/) based ingress controller.
|
||||
* [Emissary-Ingress](https://www.getambassador.io/products/api-gateway) API Gateway is an [Envoy](https://www.envoyproxy.io)-based ingress
|
||||
controller.
|
||||
* [EnRoute](https://getenroute.io/) is an [Envoy](https://www.envoyproxy.io) based API gateway that can run as an ingress controller.
|
||||
* [Easegress IngressController](https://github.com/megaease/easegress/blob/main/doc/reference/ingresscontroller.md) is an [Easegress](https://megaease.com/easegress/) based API gateway that can run as an ingress controller.
|
||||
-->
|
||||
|
@ -85,6 +83,8 @@ Kubernetes 作为一个项目,目前支持和维护
|
|||
可以用来与 Citrix Application Delivery Controller 一起使用。
|
||||
* [Contour](https://projectcontour.io/) 是一个基于 [Envoy](https://www.envoyproxy.io/)
|
||||
的 Ingress 控制器。
|
||||
* [Emissary-Ingress](https://www.getambassador.io/products/api-gateway) API 网关是一个基于
|
||||
[Envoy](https://www.envoyproxy.io/) 的入口控制器。
|
||||
* [EnRoute](https://getenroute.io/) 是一个基于 [Envoy](https://www.envoyproxy.io)
|
||||
的 API 网关,可以用作 Ingress 控制器。
|
||||
* [Easegress IngressController](https://github.com/megaease/easegress/blob/main/doc/reference/ingresscontroller.md)
|
||||
|
|
|
@ -106,10 +106,10 @@ kube-proxy 基于 `spec.internalTrafficPolicy` 的设置来过滤路由的目标
|
|||
## {{% heading "whatsnext" %}}
|
||||
|
||||
<!--
|
||||
* Read about [Topology Aware Hints](/docs/concepts/services-networking/topology-aware-hints)
|
||||
* Read about [Topology Aware Routing](/docs/concepts/services-networking/topology-aware-routing)
|
||||
* Read about [Service External Traffic Policy](/docs/tasks/access-application-cluster/create-external-load-balancer/#preserving-the-client-source-ip)
|
||||
* Follow the [Connecting Applications with Services](/docs/tutorials/services/connect-applications-service/) tutorial
|
||||
-->
|
||||
* 请阅读[拓扑感知提示](/zh-cn/docs/concepts/services-networking/topology-aware-hints)
|
||||
* 请阅读[拓扑感知路由](/zh-cn/docs/concepts/services-networking/topology-aware-hints)
|
||||
* 请阅读 [Service 的外部流量策略](/zh-cn/docs/tasks/access-application-cluster/create-external-load-balancer/#preserving-the-client-source-ip)
|
||||
* 遵循[使用 Service 连接到应用](/zh-cn/docs/tutorials/services/connect-applications-service/)教程
|
Loading…
Reference in New Issue