Load Balancer instance connection

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 connected to the service.

Manage Load Balancer instances connected to Kubernetes

Create instances

To create a Load Balancer instance connected to the 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.

Enable instance property

You can set properties of an instance created through the service manifest's annotation. To set instance properties, see the table below 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

There are two types of subnets for load balancer: Public Subnet and Private Subnet. Each type is required when creating a load balancer with a private or public IP assigned. When creating a load balancer, use the lbPublicSubnetNo configured by ncloud-config ConfigMap in the kube-system namespace or the Subnet ID in the lbSubnetNo field. This subnet ID can be specified to use a different subnet ID using the service.beta.kubernetes.io/ncloud-load-balancer-subnet-id annotation when creating a load balancer.

1. Public Subnet (Internet Gateway only)
A public subnet is required to create a load balancer with an public IP assigned. Users may request an public IP from the VPC > Public IP menu on the NAVER Cloud Platform console and assign it to a load balancer. If no public IP is specified, a new public IP will be applied.

2. Private Subnet
This subnet is required to create a load balancer in the private subnet assigned with a private IP within VPC.

Examples of instance property settings

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

Example of Network Proxy Load Balancer (NPLB) instance creation

An example of creating a NPLB instance connected to Kubernetes is shown as follows.

1. Save the following code example as an nks-lb.yml file.

• You can see the annotation to create a private network proxy type load balancer instance in the code example shown below.

apiVersion: apps/v1
kind: Deployment
metadata:
  name: my-nginx
spec:
  replicas: 1
  selector:
    matchLabels:
      run: my-nginx
  template:
    metadata:
      labels:
        run: my-nginx
    spec:
      containers:
      - name: my-nginx
        image: nginx
        ports:
        - containerPort: 80
---

kind: Service
apiVersion: v1
metadata:
  name: my-nginx
  annotations:
    service.beta.kubernetes.io/ncloud-load-balancer-layer-type: "nplb"
    service.beta.kubernetes.io/ncloud-load-balancer-internal: "true"    
    service.beta.kubernetes.io/ncloud-load-balancer-size: "SMALL"
spec:
  ports:
  - port: 80
    targetPort: 80
  selector:
    run: my-nginx
  type: LoadBalancer

2. Run the kubectl apply -f nks-lb.yml command to deploy.

Example of Network Load Balancer (NLB) instance creation

1. Save the following code example as an nks-lb.yml file.

• You can see the annotation to create a private network proxy type load balancer instance in the code example shown below.

apiVersion: apps/v1
kind: Deployment
metadata:
  name: my-nginx
spec:
  replicas: 1
  selector:
    matchLabels:
      run: my-nginx
  template:
    metadata:
      labels:
        run: my-nginx
    spec:
      containers:
      - name: my-nginx
        image: nginx
        ports:
        - containerPort: 80
---

kind: Service
apiVersion: v1
metadata:
  name: my-nginx
  annotations:
    service.beta.kubernetes.io/ncloud-load-balancer-layer-type: "nlb"
    service.beta.kubernetes.io/ncloud-load-balancer-internal: "true"    
    service.beta.kubernetes.io/ncloud-load-balancer-size: "SMALL"
spec:
  ports:
  - port: 80
    targetPort: 80
  selector:
    run: my-nginx
  type: LoadBalancer

2. Run the kubectl apply -f nks-lb.yml command to deploy.

Check the external IP of a created load balancer instance

Run the command shown 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. The following is an example of 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 which is created as LoadBalancer type to automatically delete the connected load balancer instance with it.

The following describes how to check the Kubernetes service created as LoadBalancer type and delete it.

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

• Each service's type 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