Load Balancer instance integrations

Available in VPC

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

Manage Load Balancer instances integrated with Kubernetes

Create an instance

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

• nplb: Creates a Network Proxy Load Balancer (NPLB) instance.
• nlb: Creates a Network Load Balancer (NLB) instance.

Configure instance properties

You can configure instance properties using annotations in the service manifest. To configure instance properties, set the metadata.annotations values according to the table below when creating the instance.

• Network Proxy Load Balancer (NPLB)

• Network Load Balancer (NLB)

Public and private IP assignment methods based on the Load Balancer subnet type

Load Balancer subnets are classified into two types: Public Subnet and Private Subnet. Each type is required to create a Load Balancer with a public or private IP assigned, respectively. When creating a Load Balancer, the Subnet ID defined in the lbPublicSubnetNo and lbSubnetNo fields of the ncloud-config ConfigMap in the kube-system namespace is used. You can specify a different Subnet ID by using the service.beta.kubernetes.io/ncloud-load-balancer-subnet-id annotation when creating a Load Balancer.

1. Public Subnet (for Internet gateway only)
A Public Subnet is required to create a Load Balancer with a public IP assigned. In the VPC environment of the NAVER Cloud Platform console, navigate to Menu > Services > Networking > VPC > Public IP. If you do not specify a public IP, a new one is automatically requested.

2. Private Subnet
A Private Subnet is required to create a Load Balancer with a private IP assigned within a VPC.

Examples of configuring instance properties

For detailed examples of configuring instance properties, see Load Balancer property configuration examples.

Check the external IP of the created Load Balancer instance

To check the external IP of the created instance, run the following command:

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

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

$ 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 an instance

Deleting a Kubernetes Service created with type LoadBalancer also automatically deletes the integrated Load Balancer instance.
To check and delete a Kubernetes Service created with type LoadBalancer:

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

• You can check the type of each Service in the TYPE column of the results.

$ kubectl --kubeconfig $KUBE_CONFIG get service

2. Run the following command to delete the Service with type LoadBalancer:

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