You can now configure backend Linodes within a VPC to serve NodeBalancer traffic. Communication between the NodeBalancer and backend nodes takes place over the VPC network.

New

VPCs. Added new endpoints that provide information about the VPC configurations used with a NodeBalancer. New operations and responses:

• List VPC configurations. GET /nodebalancers/{nodeBalancerId}/vpcs
• Get a VPC configuration. GET /nodebalancers/{nodeBalancerId}/vpcs/{nodeBalancerVpcConfigId}

Changed

NodeBalancers. Introduced new configurable fields—subnet_id, ipv4_range and ipv4_range_auto_assign—within the vpcs array for NodeBalancers to route traffic to VPC backends. The specified VPC subnet must exist within the same data center as the NodeBalancer, and the provided IP range must be contained within the subnet's CIDR block. All IP addresses within the specified range must be free and available for assignment.

Only one VPC can be associated with a NodeBalancer configuration. After a NodeBalancer is attached to a VPC and its subnet, neither the VPC nor the subnet can be deleted unless they are first removed from the NodeBalancer.

Updated operation:

• Create a NodeBalancer. (POST /nodebalancers)

NodeBalancer Configurations. Added a new configurable field for backend nodes that are in a VPC; subnet_id . You can have both VPC and non-VPC nodes on the same NodeBalancer configuration. Updated operations and responses:

• Rebuild a config (POST /nodebalancers/{nodeBalancerId}/configs/{configId}/rebuild)

NodeBalancer Nodes. Added a new configurable field for backend nodes that are in a VPC; subnet_id . Updated the address field to include supported IP types for non-VPC backend nodes and backend nodes within a VPC. Updated operations and responses:

• Create a node (POST /nodebalancers/{nodeBalancerId}/configs/{configId}/nodes)
• List nodes (GET /nodebalancers/{nodeBalancerId}/configs/{configId}/nodes)
• Get a NodeBalancer's node (GET /nodebalancers/{nodeBalancerId}/configs/{configId}/nodes/{nodeId})
• Update a node (PUT /nodebalancers/{nodeBalancerId}/configs/{configId}/nodes/{nodeId})