What is the difference between Ingress and NodePort/LoadBalancer services?

The main differences between Ingress and NodePort/LoadBalancer services in Kubernetes are as follows:

Ingress

1. Layer: Ingress operates at Layer 7 (HTTP/HTTPS) and provides advanced routing capabilities based on the request's URL path or hostname.
2. Routing: It can route traffic to multiple services based on rules defined in the Ingress resource, allowing for path-based and host-based routing.
3. Single Entry Point: Ingress provides a single entry point for external traffic, which can simplify access management and reduce the number of exposed IP addresses.
4. SSL/TLS Termination: Ingress can handle SSL/TLS termination, allowing secure connections to be managed at the Ingress level.
5. Additional Features: Ingress can support features like authentication, rate limiting, and more complex routing rules.

NodePort/LoadBalancer Services

1. Layer: NodePort and LoadBalancer services operate at Layer 4 (TCP/UDP) and do not provide advanced HTTP routing capabilities.
2. Direct Access: NodePort exposes a service on a specific port on each node in the cluster, while LoadBalancer provisions an external load balancer that routes traffic to the service.
3. Multiple Exposures: Each service of type NodePort or LoadBalancer requires its own external IP or port, which can lead to multiple exposed endpoints for different services.
4. Simplicity: NodePort and LoadBalancer services are simpler to set up for basic use cases, as they do not require additional configuration for routing rules.
5. No SSL/TLS Termination: While you can configure SSL/TLS termination at the application level, NodePort and LoadBalancer services do not handle it natively.

Summary

• Use Ingress when you need advanced routing capabilities, a single entry point for multiple services, and features like SSL termination.
• Use NodePort or LoadBalancer for simpler use cases where you want to expose a service directly without the need for complex routing.