nodes
Creates, updates, deletes, gets or lists a nodes resource.
Overview
| Name | nodes |
| Type | Resource |
| Id | linode.nodebalancers.nodes |
Fields
The following fields are returned by SELECT queries:
- get_node_balancer_node
- get_node_balancer_config_nodes
Methods
The following methods are available for this resource:
| Name | Accessible by | Required Params | Optional Params | Description |
|---|---|---|---|---|
get_node_balancer_node | select | Returns information about a single Node, a backend for this NodeBalancer's configured port. Learn more... Learn more... | ||
get_node_balancer_config_nodes | select | page, page_size | Returns a paginated list of NodeBalancer nodes associated with this Config. These are the backends that will be sent traffic for this port. Learn more... Learn more... | |
post_node_balancer_node | insert | data__label, data__address | 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.> 🚧 > > 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. CLI: TCP, HTTP, HTTPS. <br /> linode-cli nodebalancers node-create \<br /> 12345 4567 \<br /> --address 10.0.0.45:80 \<br /> --label node54321 \<br /> --weight 50 \<br /> --mode accept \<br /> --subnet_id 1<br /> Learn more... - CLI: UDP. <br /> linode-cli nodebalancers node-create \<br /> 12345 4567 \<br /> --address 192.168.210.120:80 \<br /> --label node54321 \<br /> --weight 50<br /> Learn more... Learn more... | |
put_node_balancer_node | replace | Updates information about a node, a backend for this NodeBalancer's configured port. > 🚧 > > 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. CLI: TCP, HTTP, HTTPS. <br /> linode-cli nodebalancers node-update \<br /> 12345 4567 54321 \<br /> --address 192.168.210.120:80 \<br /> --label node54321 \<br /> --weight 50 \<br /> --mode accept<br /> Learn more... - CLI: UDP. <br /> linode-cli nodebalancers node-create \<br /> 12345 4567 \<br /> --address 192.168.210.120:80 \<br /> --label node54321 \<br /> --weight 50<br /> Learn more... Learn more... | ||
delete_node_balancer_config_node | delete | Deletes a Node from this Config. This backend will no longer receive traffic for the configured port of this NodeBalancer. This does not change or remove the Linode whose address was used in the creation of this Node. Learn more... Learn more... |
Parameters
Parameters can be passed in the WHERE clause of a query. Check the Methods section to see which parameters are required or optional for each operation.
| Name | Datatype | Description |
|---|---|---|
page | integer | The page of a collection to return. |
page_size | integer | The number of items to return per page. |
SELECT examples
- get_node_balancer_node
- get_node_balancer_config_nodes
Returns information about a single Node, a backend for this NodeBalancer's configured port.
Learn more...
Learn more...
SELECT
*
FROM linode.nodebalancers.nodes;
Returns a paginated list of NodeBalancer nodes associated with this Config. These are the backends that will be sent traffic for this port.
Learn more...
Learn more...
SELECT
data,
page,
pages,
results
FROM linode.nodebalancers.nodes
WHERE page = '{{ page }}'
AND page_size = '{{ page_size }}';
INSERT examples
- post_node_balancer_node
- Manifest
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.
> 🚧
>
> 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. CLI: TCP, HTTP, HTTPS.
<br /> linode-cli nodebalancers node-create \<br /> 12345 4567 \<br /> --address 10.0.0.45:80 \<br /> --label node54321 \<br /> --weight 50 \<br /> --mode accept \<br /> --subnet_id 1<br />
Learn more...
- CLI: UDP.
<br /> linode-cli nodebalancers node-create \<br /> 12345 4567 \<br /> --address 192.168.210.120:80 \<br /> --label node54321 \<br /> --weight 50<br />
Learn more...
Learn more...
INSERT INTO linode.nodebalancers.nodes (
)
SELECT
;
# Description fields are for documentation purposes
- name: nodes
props:
REPLACE examples
- put_node_balancer_node
Updates information about a node, a backend for this NodeBalancer's configured port.
> 🚧
>
> 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. CLI: TCP, HTTP, HTTPS.
<br /> linode-cli nodebalancers node-update \<br /> 12345 4567 54321 \<br /> --address 192.168.210.120:80 \<br /> --label node54321 \<br /> --weight 50 \<br /> --mode accept<br />
Learn more...
- CLI: UDP.
<br /> linode-cli nodebalancers node-create \<br /> 12345 4567 \<br /> --address 192.168.210.120:80 \<br /> --label node54321 \<br /> --weight 50<br />
Learn more...
Learn more...
REPLACE linode.nodebalancers.nodes
SET
-- No updatable properties
WHERE
;
DELETE examples
- delete_node_balancer_config_node
Deletes a Node from this Config. This backend will no longer receive traffic for the configured port of this NodeBalancer.
This does not change or remove the Linode whose address was used in the creation of this Node.
Learn more...
Learn more...
DELETE FROM linode.nodebalancers.nodes;