Integrating Load Balancer instances

The latest service changes have not yet been reflected in this content. We will update the content as soon as possible. Please refer to the Korean version for information on the latest updates.

Available in VPC

When you create a service to use Ncloud Kubernetes Service, you can automatically create a Load Balancer instance which is integrated to the service.

Manage Load Balancer instances integrated to Kubernetes

Create instances

To create a Load Balancer instance integrated to Ncloud Kubernetes Service, specify the service manifest type as LoadBalancer and set the service.beta.kubernetes.io/ncloud-load-balancer-layer-type annotation as nplb or nlb.

• nplb: A network proxy load balancer (NPLB) instance is created.
• nlb: A network load balancer (NLB) instance is created.

Configure instance properties

You can set properties of an instance created through the service manifest's annotation. To set instance properties, see the following table and enter the metadata.annotations value when creating an instance.

• Network Proxy Load Balancer (NPLB)

• Network Load Balancer (NLB)

Public/private IP assignment method according to Load Balancer's subnet type

Load balancers use two types of subnets: public subnet and private subnet. Each type is required when creating a load balancer with a private or public IP assigned. When you create a load balancer, it uses the lbPublicSubnetNo and lbSubnetNo subnet IDs defined in the ncloud-config ConfigMap for the kube-system namespace. You can override the subnet ID and use different subnet IDs for the load balancer by setting the service.beta.kubernetes.io/ncloud-load-balancer-subnet-id annotation when you create it.

1. Public Subnet (for Internet Gateway only)
You need a public subnet to create a load balancer with a public IP. In the NAVER Cloud Platform console VPC environment, navigate to > Services > Networking > VPC > Public IP to request a public IP, and assign it to the load balancer. If no public IP is specified, a new public IP is applied.

2. Private Subnet
You need a private subnet in the VPC to create a load balancer with a private IP.

Instance properties settings example

For more detailed example of setting instance properties, see Load Balancer properties settings examples.

Check external IP of the created load balancer instance

Run the command below to check the external IP of a created instance.

$ kubectl --kubeconfig $KUBE_CONFIG get svc example-service

The external IP of the instance is displayed in the EXTERNAL-IP column. Below is an example viewing an external IP using the command.

$ kubectl --kubeconfig $KUBE_CONFIG get svc example-service
NAME              TYPE           CLUSTER-IP       EXTERNAL-IP    PORT(S)          AGE
example-service   LoadBalancer   172.16.101.104   10.39.10.118   8765:30365/TCP   2m11s

Delete instance

Delete the Kubernetes service created with "LoadBalancer" as its type to automatically delete the connected Load Balancer instance with it.
To check and delete a Kubernetes service created as "LoadBalancer":

1. Run the following command to check the created Kubernetes service:

• The type of each service can be seen in the result's TYPE column.

$ kubectl --kubeconfig $KUBE_CONFIG get service

2. Run the following command to delete the "LoadBalancer" type service:

$ kubectl --kubeconfig $KUBE_CONFIG delete service my-nginx