Creates a backend node that can receive traffic for the NodeBalancer configuration. Requests are routed to backend nodes on the specified port based on their status. The configurable fields for the backend node depend on the chosen protocol and whether the node is located within a Linode VPC.

After creating a NodeBalancer backend node, account administrators can add a lock to prevent accidental node deletion by using the Create a resource lock operation.

🚧

You can configure UDP on the same NodeBalancer that also uses TCP, HTTP, or HTTPS, but only when managing it through the API. If UDP is configured and you make changes to the TCP, HTTP or HTTPS settings in Cloud Manager, the existing UDP configuration will be overwritten. This is because Cloud Manager doesn't currently support UDP.

Permissions and scopes

To call this operation, you need permissions, based on the model you're using:

• Identity and access permissions. Your user needs a role with these permissions. Learn more.

  • Permissions: create_nodebalancer_config_node

• OAuth scopes. Your user needs these scopes assigned. Learn more.

  • Scopes: nodebalancers:read_write

CLI

TCP, HTTP, HTTPS

linode-cli nodebalancers node-create \
  12345 4567 \
  --address 10.0.0.45:80 \
  --label node54321 \
  --weight 50 \
  --mode accept \
  --subnet_id 1

UDP

linode-cli nodebalancers node-create \
  12345 4567 \
  --address 192.168.210.120:80 \
  --label node54321 \
  --weight 50

Learn more