Data Source: oci_network_load_balancer_backends
This data source provides the list of Backends in Oracle Cloud Infrastructure Network Load Balancer service.
Lists the backend servers for a given network load balancer and backend set.
Example Usage
data "oci_network_load_balancer_backends" "test_backends" {
#Required
backend_set_name = oci_network_load_balancer_backend_set.test_backend_set.name
network_load_balancer_id = oci_network_load_balancer_network_load_balancer.test_network_load_balancer.id
}
Argument Reference
The following arguments are supported:
backend_set_name- (Required) The name of the backend set associated with the backend servers. Example:example_backend_setnetwork_load_balancer_id- (Required) The OCID of the network load balancer to update.
Attributes Reference
The following attributes are exported:
backend_collection- The list of backend_collection.
Backend Reference
The following attributes are exported:
ip_address- The IP address of the backend server. Example:10.0.0.3is_backup- Whether the network load balancer should treat this server as a backup unit. Iftrue, then the network load balancer forwards no ingress traffic to this backend server unless all other backend servers not marked as “isBackup” fail the health check policy. Example:falseis_drain- Whether the network load balancer should drain this server. Servers marked “isDrain” receive no incoming traffic. Example:falseis_offline- Whether the network load balancer should treat this server as offline. Offline servers receive no incoming traffic. Example:falsename- A read-only field showing the IP address/IP OCID and port that uniquely identify this backend server in the backend set. Example:10.0.0.3:8080, orocid1.privateip..oc1.<var><unique_ID></var>:443or10.0.0.3:0port- The communication port for the backend server. Example:8080target_id- The IP OCID/Instance OCID associated with the backend server. Example:ocid1.privateip..oc1.<var><unique_ID></var>weight- The network load balancing policy weight assigned to the server. Backend servers with a higher weight receive a larger proportion of incoming traffic. For example, a server weighted ‘3’ receives three times the number of new connections as a server weighted ‘1’. For more information about network load balancing policies, see Network Load Balancer Policies. Example:3