Docs

Volcengine Kubernetes Engine

ALB Ingress

Using ALB Ingresses for service deployment

An Application Load Balancer (ALB) Ingress, built on the Volcano Engine ALB, offers more comprehensive Layer 7 load balancing capabilities. This topic introduces how to release services by using ALB Ingresses and related considerations.

warning

It is highly recommended that you first read Considerations for using ALB Ingresses carefully before getting started.

Limit

To prevent ALB exceptions, do not directly modify an ALB instance, its listeners, back-end server groups, or forwarding rules managed by an ALB Ingress from the ALB console. Any such modifications are undertaken at your own risk.

Do not modify any content prefixed with k8s_ in the name of a listener or backend server group.

Do not modify any content prefixed with k8s_ in the description of a forwarding rule.

Using the ALB console to modify resources and configurations specified or maintained by an ALB Ingress (for example, forwarding rules) may cause configurations to be overwritten.

Using ALB incurs fees for the use of cloud infrastructure resources. For details, see ALB billing.

Procedure

Step 1: Create an ALBInstance

In the left navigation bar, click Cluster.

On the Cluster page, click the name of the target cluster.

In the left navigation bar, click Workload > Resource Explorer. Click Create with Yaml to create an ALBInstance.

Select Custom from the Type drop-down menu.

Edit the configurations in the Yaml box.

tip

In this example, the ALBInstance will be created using an existing ALB instance, which only requires a simple configuration. For more configuration details, see Creating ALB Ingresses by using kubectl.

After the ALBInstance resource is created, click albinstance on the Resource Explorer page to view details of the resource.

Step 2: Deploy an application and service

Create the YAML file of the workload. The code of the sample file deployment-demo.yaml is as follows:

Run the following command to create the workload.

A YAML file for creating the service. The code of the sample file deployment-demo.yaml is as follows:

warning

When the network model of the cluster is Flannel, you can select only a NodePort or LoadBalancer service.

When the network model of the cluster is VPC-CNI:

If the LB-to-pod direct access mode is enabled for the Ingress, you can select a NodePort, LoadBalancer, or ClusterIP service.

If the LB-to-pod direct access mode is not enabled for the Ingress, you can select only a NodePort or LoadBalancer service.

Execute the following command to create a service.

Step 3: Create an ALB Ingress

Create a YAML file for the Ingress. The following alb-ingress.yaml file provides an example:

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: alb-ingress-demo # The name of the Ingress.
namespace: default # Namespace of the Ingress
spec:
ingressClassName: alb # The name of the ALBInstance.
rules:
- host: example.com # Domain names for external access
http:
paths:
- pathType: Prefix # Path matching rule, with Prefix (prefix matching) as the default setting.
path: / # The matching path for the request.
backend:
service:
name: service-demo # The name of the service to forward requests to.
port:
number: 80 # The service port number to forward to.

tip

This example uses the simplest method to create an ALB Ingress. For more configuration details, see Creating ALB Ingresses by using kubectl.

Run the following command to create the ALB Ingress.

kubectl apply -f alb-ingress.yaml

Validating results

Access the service by using the domain name configured in the ALB Ingress.

The response similar to the following indicates that the back-end service can be accessed through the ALB Ingress.

Last updated: 2026.04.15 11:43:37