HTTP Web 服务器和 Ingress 之间的区别？
Differences between HTTP Web Server and Ingress?
我正在学习 k8s 的世界，有很多关于入口和入口控制器的讨论。从概念上讲，它听起来与 Web 服务器相同，我将 Web 服务器定义为将 HTTP 请求代理到 Web 应用程序服务器的服务。它可以提供证书并进行基本的负载平衡...
而ingress：Ingress将集群外部的HTTP和HTTPS路由暴露给集群内的服务。流量路由由 Ingress 资源上定义的规则控制。 Ingress 可以提供负载平衡、SSL 终止和基于名称的虚拟主机。
https://kubernetes.io/docs/concepts/services-networking/ingress/
他们听起来一样！那么这里到底有什么区别呢？难道只有我一个人对此感到困惑吗？
一般来说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.
最近您可以找到许多 Web 服务器，例如 Apache or Nginx。
Kubernetes Ingress 是一个 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.
有很多入口控制器，例如 Nginx、Ambassador、Apache 等
总结一下：
要使用 Ingress，您需要一些 Web Server 作为 Ingress Controller。
Kubernetes Ingress 是一个 Kubernetes object，它可以帮助用户在 Kubernetes 集群中配置 Web Server（如 Nginx）。
正如您在文档中指出的那样，它允许您配置一些 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.
我正在学习 k8s 的世界，有很多关于入口和入口控制器的讨论。从概念上讲，它听起来与 Web 服务器相同，我将 Web 服务器定义为将 HTTP 请求代理到 Web 应用程序服务器的服务。它可以提供证书并进行基本的负载平衡...
而ingress：Ingress将集群外部的HTTP和HTTPS路由暴露给集群内的服务。流量路由由 Ingress 资源上定义的规则控制。 Ingress 可以提供负载平衡、SSL 终止和基于名称的虚拟主机。 https://kubernetes.io/docs/concepts/services-networking/ingress/
他们听起来一样！那么这里到底有什么区别呢？难道只有我一个人对此感到困惑吗？
一般来说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.
最近您可以找到许多 Web 服务器，例如 Apache or Nginx。
Kubernetes Ingress 是一个 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.
有很多入口控制器，例如 Nginx、Ambassador、Apache 等
总结一下：
要使用 Ingress，您需要一些 Web Server 作为 Ingress Controller。
Kubernetes Ingress 是一个 Kubernetes object，它可以帮助用户在 Kubernetes 集群中配置 Web Server（如 Nginx）。
正如您在文档中指出的那样，它允许您配置一些 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.