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

There are two types of Load Balancer subnets: Public Subnet and Private Subnet. Each type is required to create a Load Balancer with a public IP address or private IP address, respectively.

When a load balancer is created, the subnet IDs in the lbPublicSubnetNo and lbSubnetNo fields defined in the ncloud-config ConfigMap in the kube-system namespace are used. To use a different subnet, specify the desired subnet ID in the service.beta.kubernetes.io/ncloud-load-balancer-subnet-id annotation.

1. Public Subnet (for Internet gateway only)
A Public Subnet is required to create a Load Balancer with a public IP address. In the VPC environment of the NAVER Cloud Platform console, navigate to Menu > All Services > Networking > VPC > Public IP to request a public IP address, and then assign it to the Load Balancer. 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.

Specify multi-zone subnet IDs

When creating a Network Proxy Load Balancer (NPLB) in a multi-zone cluster, you can specify a dedicated load balancer subnet ID for each zone in the service.beta.kubernetes.io/ncloud-load-balancer-subnet-id annotation. When specifying NPLB subnet IDs in a multi-zone cluster, note the following:

• Separate multiple subnet IDs with commas (,).
• Only 1 dedicated load balancer subnet can be specified for each zone.
• Load balancer creation fails if 2 or more subnet IDs belonging to the same zone are specified.
• subnet-id value is applied only when the load balancer is created. To change the subnets of an existing load balancer, recreate the load balancer.
• Multi-zone subnet configuration is supported only for NPLBs. Network Load Balancers (NLBs) do not support multi-zone subnet configuration.
• When multi-zone subnets are specified, a public IP address cannot be assigned.

metadata:
  annotations:
    service.beta.kubernetes.io/ncloud-load-balancer-layer-type: "nplb"
    service.beta.kubernetes.io/ncloud-load-balancer-subnet-id: "123456,234567"

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

Pause Load Balancer management

lb.ncloud.naver.com/pause: "true" is a pause option available for KVM clusters running Kubernetes 1.36 or later. When this value is set, the controller's spec/provider reconciliation is paused.

Delete an instance

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

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 LoadBalancer type service:

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