Configure for a Network Load Balancer

On the [Integrate with Network Load Balancer] page, we have shown you how to install VNGCloud Controller Manager, create and apply yaml file. The following are detailed meanings of the information you can set in the yaml file:

Annotations

Use the annotations below to customize the Load Balancer to suit your needs:

Annotations	Required/Not required	Meaning
vks.vngcloud.vn/load-balancer-id	Optional	If you do not already have a previously initialized Network Load Balancer on the vLB system. We will automatically create 1 NLB on your cluster. This NLB will be displayed on vLB Portal, details can be accessed here If you already have a previously initialized Network Load Balancer on the vLB system and you want to reuse the NLB for your cluster. Now, please enter the Load Balancer ID information into this annotation.
vks.vngcloud.vn/load-balancer-name	Optional	Annotation vks.vngcloud.vn/load-balancer-namewill be used if you do not use annotation load-balancer-id. Annotation vks.vngcloud.vn/load-balancer-name only makes sense when you create a new load balancer. After the load balancer is successfully created, this annotation will be automatically deleted . Using this annotation after the load balancer has been created will have no effect . When you use this annotation, if you do not already have a previously initialized Network Load Balancer on the vLB system. We will automatically create 1 NLB on your cluster. This ALB will be displayed on vLB Portal, details can be accessed here If you already have a previously initialized Network Load Balancer on the vLB system and you want to reuse the NLB for your cluster. Now, please enter the Load Balancer Name information into this annotation.
vks.vngcloud.vn/package-id	Optional	If you do not enter this information, we will use the NLB Small configuration by default. If you already have an ACTIVE vLB host and you want to integrate this host into your K8S cluster, please skip this information field.
vks.vngcloud.vn/tags	Optional	The tag is added to your NLB.
vks.vngcloud.vn/scheme	Optional	Default is internet-facing , you can change it to internal depending on your needs.
vks.vngcloud.vn/security-groups	Optional	By default, a default security group will be created according to your Cluster.
vks.vngcloud.vn/inbound-cidrs	Optional	Default All CIRD: 0.0.0.0/0
vks.vngcloud.vn/healthy-threshold-count	Optional	Default 3
vks.vngcloud.vn/unhealthy-threshold-count	Optional	Default 3
vks.vngcloud.vn/healthcheck-interval-seconds	Optional	Default 30
vks.vngcloud.vn/healthcheck-timeout-seconds	Optional	Default 5
vks.vngcloud.vn/healthcheck-protocol	Optional	Default TCP . Users can select one of the values ​​TCP/ HTTP/ HTTPS/ PING-UDP
vks.vngcloud.vn/healthcheck-http-method	Optional	Default GET . User can choose one of GET / POST / PUT values
vks.vngcloud.vn/healthcheck-path	Optional	Default /
vks.vngcloud.vn/healthcheck-http-version	Optional	Default 1.0 . Users can choose one of the values ​​1.0, 1.1
vks.vngcloud.vn/healthcheck-http-domain-name	Optional	Default is empty
vks.vngcloud.vn/healthcheck-port	Optional	Default traffic port
vks.vngcloud.vn/success-codes	Optional	Default 200
vks.vngcloud.vn/idle-timeout-client	Optional	Default 50
vks.vngcloud.vn/idle-timeout-member	Optional	Default 50
vks.vngcloud.vn/idle-timeout-connection	Optional	Default 5
vks.vngcloud.vn/pool-algorithm	Optional	Default ROUND_ROBIN . The user can select one of the values ​​ROUND_ROBIN / LEAST_CONNECTIONS / SOURCE_IP
vks.vngcloud.vn/target-node-labels	Optional	Default is empty
vks.vngcloud.vn/enable-proxy-protocol	Optional	Default is empty. The user specifies a list of service names in the Load Balancer to which the Proxy Protocol will be applied.