Ingress & API Gateway
Ingress controllers (NGINX, Traefik), Gateway API, cert-manager, TLS termination, troubleshooting ingress routing
1What is the main role of an Ingress in Kubernetes?
What is the main role of an Ingress in Kubernetes?
답변
An Ingress exposes HTTP and HTTPS services from outside the cluster to internal services, with rule-based routing (hosts, paths). It allows managing multiple services via a single public IP, unlike LoadBalancer services which require one IP per service. Ingress also provides TLS termination, redirects, and content-based routing.
2What is the difference between an Ingress and a LoadBalancer type Service?
What is the difference between an Ingress and a LoadBalancer type Service?
답변
A LoadBalancer Service creates a dedicated cloud load balancer with a unique public IP per service, which can be expensive with multiple services. An Ingress uses a single entry point (one IP) to route traffic to multiple backend services via routing rules (host-based, path-based). Ingress requires an Ingress Controller to function, while LoadBalancer is managed directly by the cloud provider.
3What is an Ingress Controller in Kubernetes?
What is an Ingress Controller in Kubernetes?
답변
An Ingress Controller is a component that watches the Kubernetes API for Ingress resources, then automatically configures a reverse proxy (like NGINX, Traefik, HAProxy) to implement the defined routing rules. Unlike other Kubernetes controllers that are integrated by default, the Ingress Controller must be installed separately. It translates Ingress rules into actual proxy configuration.
What are the most popular Ingress Controllers in 2025?
How to configure host-based routing with Ingress?
+17 면접 질문