Skip to main content

okustera_loadbalancer_member (Resource)

The okustera_loadbalancer_member resource attaches a backend target (compute instance IP, container endpoint, or service address) to an Octavia backend pool in Okustera.

Example Usage​

Attaching Compute Instances to a Backend Pool​

resource "okustera_loadbalancer_member" "server_1" {
  pool_id       = okustera_loadbalancer_pool.web_pool.id
  address       = "192.168.10.15"
  protocol_port = 8080
  weight        = 1
  name          = "app-instance-1"
}

resource "okustera_loadbalancer_member" "server_2" {
  pool_id       = okustera_loadbalancer_pool.web_pool.id
  address       = "192.168.10.16"
  protocol_port = 8080
  weight        = 2 # Higher traffic allocation
  name          = "app-instance-2"
}

Schema​

Required​

  • pool_id (String) UUID of the backend pool to which this member belongs. (Forces replacement on change)
  • address (String) Target IPv4 address of the backend workload.
  • protocol_port (Number) Port on which the backend member listens for traffic (1–65535).

Optional​

  • name (String) Optional human-readable name of the backend member.
  • weight (Number) Traffic routing weight (1–256). Defaults to 1.
  • subnet_id (String) UUID of the subnet where the member address resides.

Read-Only​

  • id (String) Unique identifier UUID of the pool member.
  • operating_status (String) Current operating status reported by health checks (ONLINE, DRAINING, ERROR).
  • provisioning_status (String) Current provisioning state (ACTIVE, PENDING_CREATE).

Import​

Existing pool members can be imported using <pool_id>/<member_id>:

terraform import okustera_loadbalancer_member.server_1 <pool_uuid>/<member_uuid>