Kubernetes Services in AKS

  • Article

Kubernetes Services are used to logically group pods and provide network connectivity by allowing direct access to them through a specific IP address or DNS name on a designated port. This allows you to expose your application workloads to other services within the cluster or to external clients without having to manually manage the network configuration for each pod hosting a workload.

You can specify a Kubernetes ServiceType to define the type of Service you want, e.g., if you want to expose a Service on an external IP address outside of your cluster. For more information, see the Kubernetes documentation on Publishing Services (ServiceTypes).

The following ServiceTypes are available in AKS:

ClusterIP

ClusterIP creates an internal IP address for use within the AKS cluster. The ClusterIP Service is good for internal-only applications that support other workloads within the cluster. ClusterIP is used by default if you don't explicitly specify a type for a Service.

Diagram showing ClusterIP traffic flow in an AKS cluster.

NodePort

NodePort creates a port mapping on the underlying node that allows the application to be accessed directly with the node IP address and port.

Diagram showing NodePort traffic flow in an AKS cluster.

LoadBalancer

LoadBalancer creates an Azure load balancer resource, configures an external IP address, and connects the requested pods to the load balancer backend pool. To allow customers' traffic to reach the application, load balancing rules are created on the desired ports.

Diagram showing Load Balancer traffic flow in an AKS cluster.

For HTTP load balancing of inbound traffic, another option is to use an Ingress controller.

ExternalName

Creates a specific DNS entry for easier application access.

Either the load balancers and services IP address can be dynamically assigned, or you can specify an existing static IP address. You can assign both internal and external static IP addresses. Existing static IP addresses are often tied to a DNS entry.

You can create both internal and external load balancers. Internal load balancers are only assigned a private IP address, so they can't be accessed from the Internet.

Learn more about Services in the Kubernetes docs.