|
1 | | ---- |
2 | | -title: Ingress 控制器 |
3 | | -content_template: templates/concept |
4 | | -weight: 40 |
5 | | ---- |
6 | | - |
7 | | -{{% capture overview %}} |
8 | | - |
9 | | -<!-- |
10 | | -In order for the Ingress resource to work, the cluster must have an ingress controller running. |
11 | | -
|
12 | | -Unlike other types of controllers which run as part of the `kube-controller-manager` binary, Ingress controllers |
13 | | -are not started automatically with a cluster. Use this page to choose the ingress controller implementation |
14 | | -that best fits your cluster. |
15 | | -
|
16 | | -Kubernetes as a project currently supports and maintains [GCE](https://git.k8s.io/ingress-gce/README.md) and |
17 | | - [nginx](https://git.k8s.io/ingress-nginx/README.md) controllers. |
18 | | -
|
19 | | ---> |
20 | | - |
21 | | -为了让 Ingress 资源工作，集群必须有一个正在运行的 Ingress 控制器。 |
22 | | - |
23 | | -与其他类型的控制器不同，它们是作为 `kube-controller-manager` 二进制文件的一部分运行的，而 Ingress 控制器不是随集群自动启动的。 |
24 | | -通过此页面可选择最适合您的集群的 ingress 控制器实现。 |
25 | | - |
26 | | -Kubernetes 作为一个项目，目前支持和维护 [GCE](https://git.k8s.io/ingress-gce/README.md) 和 |
27 | | - [nginx](https://git.k8s.io/ingress-nginx/README.md) 控制器。 |
28 | | - |
29 | | -{{% /capture %}} |
30 | | - |
31 | | -{{% capture body %}} |
32 | | - |
33 | | -<!-- |
34 | | -## Additional controllers |
35 | | -
|
36 | | -* [Ambassador](https://www.getambassador.io/) API Gateway is an [Envoy](https://www.envoyproxy.io) based ingress |
37 | | - controller with [community](https://www.getambassador.io/docs) or |
38 | | - [commercial](https://www.getambassador.io/pro/) support from [Datawire](https://www.datawire.io/). |
39 | | -* [AppsCode Inc.](https://appscode.com) offers support and maintenance for the most widely used [HAProxy](http://www.haproxy.org/) based ingress controller [Voyager](https://appscode.com/products/voyager). |
40 | | -* [Contour](https://projectcontour.io/) is an [Envoy](https://www.envoyproxy.io/) based ingress controller |
41 | | - provided and supported by VMware. |
42 | | -* Citrix provides an [Ingress Controller](https://github.com/citrix/citrix-k8s-ingress-controller) for its hardware (MPX), virtualized (VPX) and [free containerized (CPX) ADC](https://www.citrix.com/products/citrix-adc/cpx-express.html) for [baremetal](https://github.com/citrix/citrix-k8s-ingress-controller/tree/master/deployment/baremetal) and [cloud](https://github.com/citrix/citrix-k8s-ingress-controller/tree/master/deployment) deployments. |
43 | | -* F5 Networks provides [support and maintenance](https://support.f5.com/csp/article/K86859508) |
44 | | - for the [F5 BIG-IP Controller for Kubernetes](http://clouddocs.f5.com/products/connectors/k8s-bigip-ctlr/latest). |
45 | | -* [Gloo](https://gloo.solo.io) is an open-source ingress controller based on [Envoy](https://www.envoyproxy.io) which offers API Gateway functionality with enterprise support from [solo.io](https://www.solo.io). |
46 | | -* [HAProxy Technologies](https://www.haproxy.com/) offers support and maintenance for the [HAProxy Ingress Controller for Kubernetes](https://github.com/haproxytech/kubernetes-ingress). See the [official documentation](https://www.haproxy.com/documentation/hapee/1-9r1/traffic-management/kubernetes-ingress-controller/). |
47 | | -* [Istio](https://istio.io/) based ingress controller |
48 | | - [Control Ingress Traffic](https://istio.io/docs/tasks/traffic-management/ingress/). |
49 | | -* [Kong](https://konghq.com/) offers [community](https://discuss.konghq.com/c/kubernetes) or |
50 | | - [commercial](https://konghq.com/kong-enterprise/) support and maintenance for the |
51 | | - [Kong Ingress Controller for Kubernetes](https://github.com/Kong/kubernetes-ingress-controller). |
52 | | -* [NGINX, Inc.](https://www.nginx.com/) offers support and maintenance for the |
53 | | - [NGINX Ingress Controller for Kubernetes](https://www.nginx.com/products/nginx/kubernetes-ingress-controller). |
54 | | -* [Skipper](https://opensource.zalando.com/skipper/kubernetes/ingress-controller/) HTTP router and reverse proxy for service composition, including use cases like Kubernetes Ingress, designed as a library to build your custom proxy |
55 | | -* [Traefik](https://github.com/containous/traefik) is a fully featured ingress controller |
56 | | - ([Let's Encrypt](https://letsencrypt.org), secrets, http2, websocket), and it also comes with commercial |
57 | | - support by [Containous](https://containo.us/services). |
58 | | ---> |
59 | | -## 其他控制器 |
60 | | - |
61 | | -* [Ambassador](https://www.getambassador.io/) API 网关， 一个基于 [Envoy](https://www.envoyproxy.io) 的 ingress |
62 | | - 控制器，有着来自 [Datawire](https://www.datawire.io/) [社区](https://www.getambassador.io/docs)或[商业](https://www.getambassador.io/pro/)的支持。 |
63 | | -* [AppsCode Inc.](https://appscode.com) 为最广泛使用的基于 [HAProxy](http://www.haproxy.org/) 的 ingress 控制器 [Voyager](https://appscode.com/products/voyager) 提供支持和维护. |
64 | | -* [Contour](https://projectcontour.io/) 是一个基于 [Envoy](https://www.envoyproxy.io/) 的 ingress 控制器，它由 VMware 提供和支持。 |
65 | | -* Citrix 为其硬件（MPX），虚拟化（VPX）和 [免费容器化 (CPX) ADC](https://www.citrix.com/products/citrix-adc/cpx-express.html) 提供了一个 [Ingress 控制器](https://github.com/citrix/citrix-k8s-ingress-controller)，用于[裸金属](https://github.com/citrix/citrix-k8s-ingress-controller/tree/master/deployment/baremetal)和[云](https://github.com/citrix/citrix-k8s-ingress-controller/tree/master/deployment)部署。 |
66 | | -* F5 Networks 为 [用于 Kubernetes 的 F5 BIG-IP 控制器](http://clouddocs.f5.com/products/connectors/k8s-bigip-ctlr/latest)提供[支持和维护](https://support.f5.com/csp/article/K86859508)。 |
67 | | -* [Gloo](https://gloo.solo.io) 是一个开源的基于 [Envoy](https://www.envoyproxy.io) 的 ingress 控制器，它提供了 API 网关功能，有着来自 [solo.io](https://www.solo.io) 的企业级支持。 |
68 | | -* [HAProxy Technologies](https://www.haproxy.com/) 为 [HAProxy Ingress Controller for Kubernetes](https://github.com/haproxytech/kubernetes-ingress). See the [official documentation](https://www.haproxy.com/documentation/hapee/1-9r1/traffic-management/kubernetes-ingress-controller/) 提供支持和运维服务。 |
69 | | -* 基于 [Istio](https://istio.io/) 的 ingress 控制器[控制 Ingress 流量](https://istio.io/docs/tasks/traffic-management/ingress/)。 |
70 | | -* [Kong](https://konghq.com/) 为[用于 Kubernetes 的 Kong Ingress 控制器](https://github.com/Kong/kubernetes-ingress-controller) 提供[社区](https://discuss.konghq.com/c/kubernetes)或[商业](https://konghq.com/kong-enterprise/)支持和维护。 |
71 | | -* [NGINX, Inc.](https://www.nginx.com/) 为[用于 Kubernetes 的 NGINX Ingress 控制器](https://www.nginx.com/products/nginx/kubernetes-ingress-controller)提供支持和维护。 |
72 | | -* [Skipper](https://opensource.zalando.com/skipper/kubernetes/ingress-controller/) HTTP路由器和反向代理，用于服务组合，包括诸如Kubernetes Ingress之类的用例，被设计为用于构建自定义代理的库。 |
73 | | -* [Traefik](https://github.com/containous/traefik) 是一个全功能的 ingress 控制器 |
74 | | - （[Let's Encrypt](https://letsencrypt.org)，secrets，http2，websocket），并且它也有来自 [Containous](https://containo.us/services) 的商业支持。 |
75 | | - |
76 | | -<!-- |
77 | | -## Using multiple Ingress controllers |
78 | | -
|
79 | | -You may deploy [any number of ingress controllers](https://git.k8s.io/ingress-nginx/docs/user-guide/multiple-ingress.md#multiple-ingress-controllers) |
80 | | -within a cluster. When you create an ingress, you should annotate each ingress with the appropriate |
81 | | -[`ingress.class`](https://git.k8s.io/ingress-gce/docs/faq/README.md#how-do-i-run-multiple-ingress-controllers-in-the-same-cluster) |
82 | | -to indicate which ingress controller should be used if more than one exists within your cluster. |
83 | | -
|
84 | | -If you do not define a class, your cloud provider may use a default ingress controller. |
85 | | -
|
86 | | -Ideally, all ingress controllers should fulfill this specification, but the various ingress |
87 | | -controllers operate slightly differently. |
88 | | ---> |
89 | | -## 使用多个 Ingress 控制器 |
90 | | - |
91 | | -你可以在集群中部署[任意数量的 ingress 控制器](https://git.k8s.io/ingress-nginx/docs/user-guide/multiple-ingress.md#multiple-ingress-controllers)。 |
92 | | -创建 ingress 时，应该使用适当的 |
93 | | -[`ingress.class`](https://git.k8s.io/ingress-gce/docs/faq/README.md#how-do-i-run-multiple-ingress-controllers-in-the-same-cluster) 注解每个 ingress |
94 | | -以表明在集群中如果有多个 ingress 控制器时，应该使用哪个 ingress 控制器。 |
95 | | - |
96 | | -如果不定义 `ingress.class`，云提供商可能使用默认的 ingress 控制器。 |
97 | | - |
98 | | -理想情况下，所有 ingress 控制器都应满足此规范，但各种 ingress 控制器的操作略有不同。 |
99 | | - |
100 | | -{{< note >}} |
101 | | -<!-- |
102 | | -Make sure you review your ingress controller's documentation to understand the caveats of choosing it. |
103 | | ---> |
104 | | -确保您查看了 ingress 控制器的文档，以了解选择它的注意事项。 |
105 | | -{{< /note >}} |
106 | | - |
107 | | -{{% /capture %}} |
108 | | - |
109 | | -{{% capture whatsnext %}} |
110 | | -<!-- |
111 | | -* Learn more about [Ingress](/docs/concepts/services-networking/ingress/). |
112 | | -* [Set up Ingress on Minikube with the NGINX Controller](/docs/tasks/access-application-cluster/ingress-minikube). |
113 | | ---> |
114 | | -* 了解更多关于 [Ingress](/docs/concepts/services-networking/ingress/)。 |
115 | | -* [在 Minikube 上使用 NGINX 控制器安装 Ingress](/docs/tasks/access-application-cluster/ingress-minikube)。 |
116 | | -{{% /capture %}} |
| 1 | +--- |
| 2 | +title: Ingress 控制器 |
| 3 | +content_template: templates/concept |
| 4 | +weight: 40 |
| 5 | +--- |
| 6 | + |
| 7 | +<!-- |
| 8 | +--- |
| 9 | +title: Ingress Controllers |
| 10 | +reviewers: |
| 11 | +content_template: templates/concept |
| 12 | +weight: 40 |
| 13 | +--- |
| 14 | +--> |
| 15 | + |
| 16 | +{{% capture overview %}} |
| 17 | + |
| 18 | +<!-- |
| 19 | +In order for the Ingress resource to work, the cluster must have an ingress controller running. |
| 20 | +
|
| 21 | +Unlike other types of controllers which run as part of the `kube-controller-manager` binary, Ingress controllers |
| 22 | +are not started automatically with a cluster. Use this page to choose the ingress controller implementation |
| 23 | +that best fits your cluster. |
| 24 | +
|
| 25 | +Kubernetes as a project currently supports and maintains [GCE](https://git.k8s.io/ingress-gce/README.md) and |
| 26 | + [nginx](https://git.k8s.io/ingress-nginx/README.md) controllers. |
| 27 | +
|
| 28 | +--> |
| 29 | + |
| 30 | +为了让 Ingress 资源工作，集群必须有一个正在运行的 Ingress 控制器。 |
| 31 | + |
| 32 | +与作为 `kube-controller-manager` 可执行文件的一部分运行的其他类型的控制器不同，Ingress 控制器不是随集群自动启动的。 |
| 33 | +基于此页面，您可选择最适合您的集群的 ingress 控制器实现。 |
| 34 | + |
| 35 | +Kubernetes 作为一个项目，目前支持和维护 [GCE](https://git.k8s.io/ingress-gce/README.md) |
| 36 | +和 [nginx](https://git.k8s.io/ingress-nginx/README.md) 控制器。 |
| 37 | + |
| 38 | +{{% /capture %}} |
| 39 | + |
| 40 | +{{% capture body %}} |
| 41 | + |
| 42 | +<!-- |
| 43 | +## Additional controllers |
| 44 | +--> |
| 45 | +## 其他控制器 |
| 46 | + |
| 47 | +<!-- |
| 48 | +* [AKS Application Gateway Ingress Controller](https://github.com/Azure/application-gateway-kubernetes-ingress) is an ingress controller that enables ingress to [AKS clusters](https://docs.microsoft.com/azure/aks/kubernetes-walkthrough-portal) using the [Azure Application Gateway](https://docs.microsoft.com/azure/application-gateway/overview). |
| 49 | +* [Ambassador](https://www.getambassador.io/) API Gateway is an [Envoy](https://www.envoyproxy.io) based ingress |
| 50 | + controller with [community](https://www.getambassador.io/docs) or |
| 51 | + [commercial](https://www.getambassador.io/pro/) support from [Datawire](https://www.datawire.io/). |
| 52 | +* [AppsCode Inc.](https://appscode.com) offers support and maintenance for the most widely used [HAProxy](http://www.haproxy.org/) based ingress controller [Voyager](https://appscode.com/products/voyager). |
| 53 | +* [AWS ALB Ingress Controller](https://github.com/kubernetes-sigs/aws-alb-ingress-controller) enables ingress using the [AWS Application Load Balancer](https://aws.amazon.com/elasticloadbalancing/). |
| 54 | +* [Contour](https://projectcontour.io/) is an [Envoy](https://www.envoyproxy.io/) based ingress controller |
| 55 | + provided and supported by VMware. |
| 56 | +* Citrix provides an [Ingress Controller](https://github.com/citrix/citrix-k8s-ingress-controller) for its hardware (MPX), virtualized (VPX) and [free containerized (CPX) ADC](https://www.citrix.com/products/citrix-adc/cpx-express.html) for [baremetal](https://github.com/citrix/citrix-k8s-ingress-controller/tree/master/deployment/baremetal) and [cloud](https://github.com/citrix/citrix-k8s-ingress-controller/tree/master/deployment) deployments. |
| 57 | +* F5 Networks provides [support and maintenance](https://support.f5.com/csp/article/K86859508) |
| 58 | + for the [F5 BIG-IP Controller for Kubernetes](http://clouddocs.f5.com/products/connectors/k8s-bigip-ctlr/latest). |
| 59 | +* [Gloo](https://gloo.solo.io) is an open-source ingress controller based on [Envoy](https://www.envoyproxy.io) which offers API Gateway functionality with enterprise support from [solo.io](https://www.solo.io). |
| 60 | +* [HAProxy Ingress](https://haproxy-ingress.github.io) is a highly customizable community-driven ingress controller for HAProxy. |
| 61 | +* [HAProxy Technologies](https://www.haproxy.com/) offers support and maintenance for the [HAProxy Ingress Controller for Kubernetes](https://github.com/haproxytech/kubernetes-ingress). See the [official documentation](https://www.haproxy.com/documentation/hapee/1-9r1/traffic-management/kubernetes-ingress-controller/). |
| 62 | +* [Istio](https://istio.io/) based ingress controller |
| 63 | + [Control Ingress Traffic](https://istio.io/docs/tasks/traffic-management/ingress/). |
| 64 | +* [Kong](https://konghq.com/) offers [community](https://discuss.konghq.com/c/kubernetes) or |
| 65 | + [commercial](https://konghq.com/kong-enterprise/) support and maintenance for the |
| 66 | + [Kong Ingress Controller for Kubernetes](https://github.com/Kong/kubernetes-ingress-controller). |
| 67 | +* [NGINX, Inc.](https://www.nginx.com/) offers support and maintenance for the |
| 68 | + [NGINX Ingress Controller for Kubernetes](https://www.nginx.com/products/nginx/kubernetes-ingress-controller). |
| 69 | +* [Skipper](https://opensource.zalando.com/skipper/kubernetes/ingress-controller/) HTTP router and reverse proxy for service composition, including use cases like Kubernetes Ingress, designed as a library to build your custom proxy |
| 70 | +* [Traefik](https://github.com/containous/traefik) is a fully featured ingress controller |
| 71 | + ([Let's Encrypt](https://letsencrypt.org), secrets, http2, websocket), and it also comes with commercial |
| 72 | + support by [Containous](https://containo.us/services). |
| 73 | +--> |
| 74 | +* [AKS 应用程序网关 Ingress 控制器]使用 [Azure 应用程序网关](https://docs.microsoft.com/azure/application-gateway/overview)启用[AKS 集群](https://docs.microsoft.com/azure/aks/kubernetes-walkthrough-portal) ingress。 |
| 75 | +* [Ambassador](https://www.getambassador.io/) API 网关， 一个基于 [Envoy](https://www.envoyproxy.io) 的 ingress |
| 76 | + 控制器，有着来自[社区](https://www.getambassador.io/docs) 的支持和来自 [Datawire](https://www.datawire.io/) 的[商业](https://www.getambassador.io/pro/) 支持。 |
| 77 | +* [AppsCode Inc.](https://appscode.com) 为最广泛使用的基于 [HAProxy](http://www.haproxy.org/) 的 ingress 控制器 [Voyager](https://appscode.com/products/voyager) 提供支持和维护。 |
| 78 | +* [AWS ALB Ingress 控制器](https://github.com/kubernetes-sigs/aws-alb-ingress-controller)通过 [AWS 应用 Load Balancer](https://aws.amazon.com/elasticloadbalancing/) 启用 ingress。 |
| 79 | +* [Contour](https://projectcontour.io/) 是一个基于 [Envoy](https://www.envoyproxy.io/) 的 ingress 控制器，它由 VMware 提供和支持。 |
| 80 | +* Citrix 为其硬件（MPX），虚拟化（VPX）和 [免费容器化 (CPX) ADC](https://www.citrix.com/products/citrix-adc/cpx-express.html) 提供了一个 [Ingress 控制器](https://github.com/citrix/citrix-k8s-ingress-controller)，用于[裸金属](https://github.com/citrix/citrix-k8s-ingress-controller/tree/master/deployment/baremetal)和[云](https://github.com/citrix/citrix-k8s-ingress-controller/tree/master/deployment)部署。 |
| 81 | +* F5 Networks 为 [用于 Kubernetes 的 F5 BIG-IP 控制器](http://clouddocs.f5.com/products/connectors/k8s-bigip-ctlr/latest)提供[支持和维护](https://support.f5.com/csp/article/K86859508)。 |
| 82 | +* [Gloo](https://gloo.solo.io) 是一个开源的基于 [Envoy](https://www.envoyproxy.io) 的 ingress 控制器，它提供了 API 网关功能，有着来自 [solo.io](https://www.solo.io) 的企业级支持。 |
| 83 | +* [HAProxy Ingress](https://haproxy-ingress.github.io) 是 HAProxy 高度可定制的、由社区驱动的 Ingress 控制器。 |
| 84 | +* [HAProxy Technologies](https://www.haproxy.com/) 为[用于 Kubernetes 的 HAProxy Ingress 控制器](https://github.com/haproxytech/kubernetes-ingress) 提供支持和维护。具体信息请参考[官方文档](https://www.haproxy.com/documentation/hapee/1-9r1/traffic-management/kubernetes-ingress-controller/)。 |
| 85 | +* 基于 [Istio](https://istio.io/) 的 ingress 控制器[控制 Ingress 流量](https://istio.io/docs/tasks/traffic-management/ingress/)。 |
| 86 | +* [Kong](https://konghq.com/) 为[用于 Kubernetes 的 Kong Ingress 控制器](https://github.com/Kong/kubernetes-ingress-controller) 提供[社区](https://discuss.konghq.com/c/kubernetes)或[商业](https://konghq.com/kong-enterprise/)支持和维护。 |
| 87 | +* [NGINX, Inc.](https://www.nginx.com/) 为[用于 Kubernetes 的 NGINX Ingress 控制器](https://www.nginx.com/products/nginx/kubernetes-ingress-controller)提供支持和维护。 |
| 88 | +* [Skipper](https://opensource.zalando.com/skipper/kubernetes/ingress-controller/) HTTP 路由器和反向代理，用于服务组合，包括诸如 Kubernetes Ingress 之类的用例，被设计为用于构建自定义代理的库。 |
| 89 | +* [Traefik](https://github.com/containous/traefik) 是一个全功能的 ingress 控制器 |
| 90 | + （[Let's Encrypt](https://letsencrypt.org)，secrets，http2，websocket），并且它也有来自 [Containous](https://containo.us/services) 的商业支持。 |
| 91 | + |
| 92 | +<!-- |
| 93 | +## Using multiple Ingress controllers |
| 94 | +--> |
| 95 | +## 使用多个 Ingress 控制器 |
| 96 | + |
| 97 | +<!-- |
| 98 | +You may deploy [any number of ingress controllers](https://git.k8s.io/ingress-nginx/docs/user-guide/multiple-ingress.md#multiple-ingress-controllers) |
| 99 | +within a cluster. When you create an ingress, you should annotate each ingress with the appropriate |
| 100 | +[`ingress.class`](https://git.k8s.io/ingress-gce/docs/faq/README.md#how-do-i-run-multiple-ingress-controllers-in-the-same-cluster) |
| 101 | +to indicate which ingress controller should be used if more than one exists within your cluster. |
| 102 | +
|
| 103 | +If you do not define a class, your cloud provider may use a default ingress controller. |
| 104 | +
|
| 105 | +Ideally, all ingress controllers should fulfill this specification, but the various ingress |
| 106 | +controllers operate slightly differently. |
| 107 | +--> |
| 108 | + |
| 109 | +你可以在集群中部署[任意数量的 ingress 控制器](https://git.k8s.io/ingress-nginx/docs/user-guide/multiple-ingress.md#multiple-ingress-controllers)。 |
| 110 | +创建 ingress 时，应该使用适当的 [`ingress.class`](https://git.k8s.io/ingress-gce/docs/faq/README.md#how-do-i-run-multiple-ingress-controllers-in-the-same-cluster) 注解每个 ingress |
| 111 | +以表明在集群中如果有多个 ingress 控制器时，应该使用哪个 ingress 控制器。 |
| 112 | + |
| 113 | +如果不定义 `ingress.class`，云提供商可能使用默认的 ingress 控制器。 |
| 114 | + |
| 115 | +理想情况下，所有 ingress 控制器都应满足此规范，但各种 ingress 控制器的操作略有不同。 |
| 116 | + |
| 117 | +<!-- |
| 118 | +Make sure you review your ingress controller's documentation to understand the caveats of choosing it. |
| 119 | +--> |
| 120 | +{{< note >}} |
| 121 | +确保您查看了 ingress 控制器的文档，以了解选择它的注意事项。 |
| 122 | +{{< /note >}} |
| 123 | + |
| 124 | +{{% /capture %}} |
| 125 | + |
| 126 | +{{% capture whatsnext %}} |
| 127 | +<!-- |
| 128 | +* Learn more about [Ingress](/docs/concepts/services-networking/ingress/). |
| 129 | +* [Set up Ingress on Minikube with the NGINX Controller](/docs/tasks/access-application-cluster/ingress-minikube). |
| 130 | +--> |
| 131 | +* 进一步了解 [Ingress](/docs/concepts/services-networking/ingress/)。 |
| 132 | +* [在 Minikube 上使用 NGINX 控制器安装 Ingress](/docs/tasks/access-application-cluster/ingress-minikube)。 |
| 133 | +{{% /capture %}} |
0 commit comments