Optionaladdress?: stringBackend nodes can be Linodes and Linodes within a VPC. The following IP types are supported:
Optional Readonlyconfig_id?: numberRead-only The NodeBalancer Config ID that this Node belongs to.
Optional Readonlyid?: numberRead-only This node's unique ID.
Optionallabel?: stringThe label for this node. This is for display purposes only.
Optionalmode?: "none"Read-only The mode this NodeBalancer should use when sending traffic to this backend. For backend nodes with a UDP config, the mode doesn't apply, so the value is none.
Optional Readonlynodebalancer_id?: numberRead-only The NodeBalancer ID that this Node belongs to.
Optionalstatus?: "unknown" | "UP" | "DOWN"Read-only The current status of this node, based on the configured checks of its NodeBalancer config.
Optionalsubnet_id?: numberRequired for VPC backend nodes only. The VPC's subnet. To display information about your VPCs and their subnets, run the List VPCs operation.
Optionalweight?: numberUsed when picking a backend to serve a request and is not pinned to a single backend yet. Nodes with a higher weight will receive more traffic.
Optionaladdress?: stringBackend nodes can be Linodes and Linodes within a VPC. The following IP types are supported:
Optional Readonlyconfig_id?: numberRead-only The NodeBalancer Config ID that this Node belongs to.
Optional Readonlyid?: numberRead-only This node's unique ID.
Optionallabel?: stringThe label for this node. This is for display purposes only.
Optionalmode?: "accept" | "reject" | "drain" | "backup"The mode this NodeBalancer should use when sending traffic to this backend.
accept this backend is accepting traffic.reject this backend will not receive traffic.drain this backend will not receive new traffic, but connections already pinned to it will continue to be routed to it.backup, this backend will only receive traffic if all accept nodes are down.Optional Readonlynodebalancer_id?: numberRead-only The NodeBalancer ID that this Node belongs to.
Optionalstatus?: "unknown" | "UP" | "DOWN"Read-only The current status of this node, based on the configured checks of its NodeBalancer Config.
Optionalsubnet_id?: numberRequired for VPC backend nodes only. The VPC's subnet. To display information about your VPCs and their subnets, run the List VPCs operation.
Optionalweight?: numberUsed when picking a backend to serve a request and is not pinned to a single backend yet. Nodes with a higher weight will receive more traffic.
The ID of the Config to access.
The ID of the NodeBalancer.
The ID of the Node to access.
Optionalquery
A NodeBalancer node represents a single backend serving requests for a single port of a NodeBalancer. Nodes are tied to individual NodeBalancer configurations and route traffic over their private IPv4 address, IPv6 address, or VPC IPv4 address. If the same Linode is serving traffic for more than one port on the same NodeBalancer, one NodeBalancer node is required for each config (port) it should serve requests on. For example, if you have four backends, and each should respond to both HTTP and HTTPS requests, you will need two NodeBalancer configs (port 80 and port 443) and four backends each, one for each of the Linodes serving requests for that port.