Kvindo™ Cloud Docs
A Load Balancer distributes incoming network traffic across multiple backend targets to improve the availability, scalability, and reliability of an application. It lives in a subnet, optionally receives traffic on a public Floating IP, and forwards it to Target Groups according to its Listeners and their Rules.
• Subnet — the VPC subnet the load balancer runs in (spec.vpcSubnetId)
• Floating IP — an optional public IP clients connect to (spec.floatingIpId)
• Tier — a reserved field for future use; only standard is accepted today
• Listeners — accept traffic on a port + protocol; Rules route it to Target Groups
• TLS certificates — HTTPS and TLS listeners can present a Certificate you supply, or have the load balancer generate one automatically via Let's Encrypt (HTTP-01 challenge) — which requires a public IP and DNS for every host already pointing at it
• Addons — optional Prometheus sidecars on the load balancer's own VM (spec.addons). Today only node_exporter, which reports the host's CPU, memory, disk and network on 9100. It binds the VM's private address only and does not authenticate, so it is never reachable from the internet; a listener on the same port is refused at submit. Empty means none, and removing an addon stops it and deletes its binary
| UI Name | API / kc name | Terraform name | Optional | Format | Default | Is read only | Description |
|---|---|---|---|---|---|---|---|
| Tier | spec.tier |
spec.tier |
No | string — standard |
standard |
No | Reserved for future use — only standard is accepted today |
| Subnet | spec.vpcSubnetId |
spec.vpc_subnet_id |
No | ULID — references a VPC Subnet | — | No | The subnet the load balancer runs in |
| Floating IP | spec.floatingIpId |
spec.floating_ip_id |
Yes | ULID (nullable) — references a Floating IP | — | No | Optional public IP clients connect to |
| Addons | spec.addons |
spec.addons |
Yes | list of {name, version} |
empty | No | Optional monitoring sidecars. Only node_exporter (1.12.1) today, on port 9100, private address only. An empty list removes whatever a previous change installed |
| Public IPv4 | status.publicIpV4 |
status.public_ipv4 |
— | string (nullable) | — | Yes | Public IPv4 the load balancer accepts traffic on |
| Public IPv6 | status.publicIpV6 |
status.public_ipv6 |
— | string (nullable) | — | Yes | Public IPv6 the load balancer accepts traffic on. IPv6 is not yet implemented — reserved for future use |
| Private IPv4 | status.privateIpV4 |
status.private_ipv4 |
— | string (nullable) | — | Yes | Private IPv4 of the load balancer inside the subnet |
| Private IPv6 | status.privateIpV6 |
status.private_ipv6 |
— | string (nullable) | — | Yes | Private IPv6 of the load balancer inside the subnet. IPv6 is not yet implemented — reserved for future use |
| Addons | status.addons |
status.addons |
— | list of name@version |
— | Yes | The addons actually installed, reported by the backing service — not the ones you asked for. The two differ while a change is in flight |
| Node exporter endpoints | status.nodeExporterEndpoints |
status.node_exporter_endpoints |
— | list of host:port |
— | Yes | Where to scrape node_exporter. Private addresses, because that is what it binds. Empty unless the addon is applied |
A standard load balancer in an existing subnet, reachable on a floating IP. Add Listeners, Rules, and Target Groups to route traffic — see the Load Balancing guide for the full stack.
Terraform
Python SDK
kc CLI
Resource docs
Examples
More in this section