Which two resources are commonly used together to expose applications to external traffic, including type options like ClusterIP, NodePort, and LoadBalancer?

Which two resources are commonly used together to expose applications to external traffic, including type options like ClusterIP, NodePort, and LoadBalancer?

• A. Services and Ingress
• B. Pods and Services
• C. ConfigMaps and Secrets
• D. Deployments and Daemons

Answer: (A)

The key idea is how Kubernetes exposes applications to outside traffic. A Service provides a stable network endpoint for a set of pods, and it can be configured with types like ClusterIP (internal), NodePort (opens a port on each node), or LoadBalancer (integrates with a cloud LB to expose it externally). An Ingress sits in front of one or more Services and defines rules for routing external HTTP(S) requests to the appropriate Service backend, often with features like host-based or path-based routing and TLS termination. In practice, you typically pair a Service with an Ingress: the Service handles the actual pods behind a stable address, and the Ingress provides flexible, externally accessible routing to those Services. An Ingress Controller is needed to implement the Ingress rules. Other resources like ConfigMaps/Secrets or workload controllers (Deployments/Daemons) aren’t used primarily for exposing external traffic, so they don’t fit this pairing.

The key idea is how Kubernetes exposes applications to outside traffic. A Service provides a stable network endpoint for a set of pods, and it can be configured with types like ClusterIP (internal), NodePort (opens a port on each node), or LoadBalancer (integrates with a cloud LB to expose it externally). An Ingress sits in front of one or more Services and defines rules for routing external HTTP(S) requests to the appropriate Service backend, often with features like host-based or path-based routing and TLS termination. In practice, you typically pair a Service with an Ingress: the Service handles the actual pods behind a stable address, and the Ingress provides flexible, externally accessible routing to those Services. An Ingress Controller is needed to implement the Ingress rules. Other resources like ConfigMaps/Secrets or workload controllers (Deployments/Daemons) aren’t used primarily for exposing external traffic, so they don’t fit this pairing.