http - HTTP Web Server 和 Ingress 的区别？

Question

我正在学习 k8s 的世界，有很多关于入口和入口 Controller 的讨论。从概念上讲，它听起来与 Web 服务器相同，我将其定义为将 HTTP 请求代理到 Web 应用程序服务器的服务。它可以提供证书并进行基本的负载平衡......
而 ingress:Ingress 将来自集群外部的 HTTP 和 HTTPS 路由暴露给集群内的服务。流量路由由 Ingress 资源上定义的规则控制。 Ingress 可以提供负载平衡、SSL 终止和基于名称的虚拟主机。
https://kubernetes.io/docs/concepts/services-networking/ingress/
他们听起来一样!那么这里究竟有什么区别呢？我不能是唯一一个被这个弄糊涂的人吧？

Answer 1

一般情况Web Server's负责接受和满足客户的要求。

A web server‘s fundamental job is to accept and fulfill requests from clients for static content from a website (HTML pages, files, images, video, and so on). The client is almost always a browser or mobile application and the request takes the form of a Hypertext Transfer Protocol (HTTP) message, as does the web server’s response.

最近你可以找到很多网络服务器，比如 Apache或 Nginx .
Kubernetes 入口 是 API object .在 IBM blog - What is Kubernetes Ingress and why is it useful?

Kubernetes Ingress is an API object that provides routing rules to manage external users' access to the services in a Kubernetes cluster, typically via HTTPS/HTTP. With Ingress, you can easily set up rules for routing traffic without creating a bunch of Load Balancers or exposing each service on the node. This makes it the best option to use in production environments.

也在 Kubernetes Ingress Docs你可以找到 Kubernetes Ingress需求 Ingress Controller .

You must have an Ingress controller to satisfy an Ingress. Only creating an Ingress resource has no effect.

有很多入口 Controller ，如 Nginx , Ambassador , Apache ， 等等。
总结一下:
使用 Ingress你需要一些 Web Server如 Ingress Controller . Kubernetes Ingress是 Kubernetes object帮助用户配置 Web Server (如 Nginx)在 Kubernetes 集群中。
正如您在文档中指出的那样，它允许您配置一些 HTTP/HTTPS路由、流量负载平衡、终止 SSL/TLS 等。

Ingress exposes HTTP and HTTPS routes from outside the cluster to services within the cluster. Traffic routing is controlled by rules defined on the Ingress resource.