ALB Ingress Controller configuration

Available in VPC

You can use the ALB Ingress Controller to integrate Kubernetes Ingress with a Load Balancer and route traffic.

When an Ingress is created in the Kubernetes system, the ALB Ingress Controller uses the values defined in the Ingress to create a Load Balancer instance. Once the instance is created, the ALB Ingress Controller creates a target group using the node port of the Service defined in the ingress rules and registers it to the instance.

Install ALB Ingress Controller

To prepare the ALB Ingress Controller after installing it in the cluster:

1. Run the command corresponding to your region to install the ALB Ingress Controller:

   Note

   Clusters with a KVM hypervisor include the ALB Ingress Controller by default, so you can use it immediately without additional installation.

   • The alb-ingress-controller is created in the kube-system namespace, along with the required ServiceAccount, ClusterRole, ClusterRoleBinding, and IngressClass.

   • Korea

     kubectl --kubeconfig=$KUBE_CONFIG apply -f https://raw.githubusercontent.com/NaverCloudPlatform/nks-alb-ingress-controller/main/docs/en/install/pub/install.yaml
     

     • For Kubernetes versions earlier than 1.19, install https://raw.githubusercontent.com/NaverCloudPlatform/nks-alb-ingress-controller/v0.3.1/docs/en/install/pub/install.yaml.

   • Singapore

     kubectl --kubeconfig=$KUBE_CONFIG apply -f https://raw.githubusercontent.com/NaverCloudPlatform/nks-alb-ingress-controller/main/docs/en/install/pub-sg/install.yaml
     

     • For Kubernetes versions earlier than 1.19, install https://raw.githubusercontent.com/NaverCloudPlatform/nks-alb-ingress-controller/v0.3.1/docs/en/install/pub-sg/install.yaml.

   • Japan

     kubectl --kubeconfig=$KUBE_CONFIG apply -f https://raw.githubusercontent.com/NaverCloudPlatform/nks-alb-ingress-controller/main/docs/en/install/pub-jp/install.yaml
     

     • For Kubernetes versions earlier than 1.19, install https://raw.githubusercontent.com/NaverCloudPlatform/nks-alb-ingress-controller/v0.3.1/docs/en/install/pub-jp/install.yaml.

2. Verify that the ALB Ingress Controller is in the running state.

kubectl --kubeconfig=$KUBE_CONFIG get pods -n kube-system -l app.kubernetes.io/name=alb-ingress-controller

3. Add the spec.ingressClassName: alb field to the Ingress resources.
   • For Kubernetes versions earlier than 1.19, add the kubernetes.io/ingress.class: alb annotation.

ALB Ingress Controller configuration and annotations

Default ALB Ingress Controller configuration

The following describes the default configuration for the ALB Ingress Controller:

• Service type: NodePort
  All services to be exposed through an Ingress must be created with the NodePort type.
• Default Rule
  The default rule is applied when no other rules match and can be configured in spec.defaultBackend.
  Additional rules or use-annotation settings cannot be configured for the default rule. If a default rule is not configured, a default target group set to port 80 is created.
• Rule Priority
  Rule priority is determined by the order of rules defined in the Ingress. The first rule in the list is assigned priority 1.

ALB Ingress Controller annotations

You can use annotations on Kubernetes Ingress and service objects to change settings.

Refer to the table below for the required annotations. All ALB Ingress Controller annotations start with alb.ingress.kubernetes.io/.

• alb.ingress.kubernetes.io/actions.${actionName}: You can configure additional listener rule features by providing a JSON-formatted string that follows the actions model. To apply the annotation, set service.name of the ingress rule to ${actionName} and set service.port.name to use-annotation.

• alb.ingress.kubernetes.io/conditions.${conditionName}: You can configure additional conditions beyond the Host and Path rules defined in the Ingress by providing a JSON-formatted string that follows the conditions model. These conditions are applied to the service with a serviceName that matches ${conditionName} in the ingress rule.

Example codes

For more detailed examples of the ALB Ingress Controller, see ALB Ingress Controller use cases.