Kvindo™ Cloud Docs
A VPC Peering Peer is one Kvindo-side member of a VPC Peering. It attaches a subnet and a floating IP to the peering so its resources become reachable over private IPs from the other side.
• VPC Peering — the peering this member joins (spec.vpcPeeringId)
• Subnet — the Kvindo subnet exposed over the peering (spec.vpcSubnetId)
• Floating IP — public IP for the peer endpoint (spec.floatingIpId)
• Assigned IPs — the peer's own public/private addresses are reported in status
spec.floatingIpId — its private IP is
reported back as status.privateIpV4. That gateway VM is the only host in the
subnet reachable automatically over the peering; anything else needs a Route Table Route
pointing at that status.privateIpV4, plus a Security Group rule on the
destination VM allowing the peer's CIDR. See the VPC Peering page for the
full worked example.
spec.addons is optional and empty by default. Today the
catalog offers node_exporter 1.12.1, which is installed on this peer's VM and
serves /metrics on the peer's private address at port 9100 — reported back as
status.nodeExporterEndpoint. It binds the private interface only (the exporter does not
authenticate, and a peer VM carries no security group, so a public bind would publish host metrics), so
scrape it from inside the VPC or over the peering. Removing an entry is a real instruction: the next
reconcile stops the unit and deletes the binary. Addons are scoped per peer — never per peering.
28079, exposing a
/metrics endpoint with peer ids/IPs and per-direction tunnel health. It is
reachable only from the private network (not from the public internet).
| UI Name | API / kc name | Terraform name | Optional | Format | Default | Is read only | Description |
|---|---|---|---|---|---|---|---|
| VPC Peering | spec.vpcPeeringId |
spec.vpc_peering_id |
No | ULID — references a VPC Peering | — | No | The peering this member joins (immutable after creation) |
| VPC Subnet | spec.vpcSubnetId |
spec.vpc_subnet_id |
No | ULID — references a VPC Subnet | — | No | The Kvindo subnet exposed over the peering |
| Floating IP | spec.floatingIpId |
spec.floating_ip_id |
No | ULID — references a Floating IP | — | No | Public IP for the peer endpoint |
| Addons | spec.addons |
spec.addons |
No | list of {name, version} | [] | Yes | Optional metrics sidecars installed on THIS peer's VM. Empty = none. Removal is a real instruction |
| Public IPv4 | status.publicIpV4 |
status.public_ipv4 |
— | string (nullable) | — | Yes | Public IPv4 of the peer endpoint |
| Public IPv6 | status.publicIpV6 |
status.public_ipv6 |
— | string (nullable) | — | Yes | Public IPv6 of the peer endpoint. IPv6 is not yet implemented — reserved for future use |
| Private IPv4 | status.privateIpV4 |
status.private_ipv4 |
— | string (nullable) | — | Yes | Private IPv4 of the peer endpoint |
| Private IPv6 | status.privateIpV6 |
status.private_ipv6 |
— | string (nullable) | — | Yes | Private IPv6 of the peer endpoint. IPv6 is not yet implemented — reserved for future use |
| Addons | status.addons |
status.addons |
— | string[] | [] | Yes | The addons actually INSTALLED on this VM, as name@version — the applied answer, not the requested one |
| node_exporter endpoint | status.nodeExporterEndpoint |
status.node_exporter_endpoint |
— | string (nullable) | — | Yes | private-ip:9100 on this peer's private address, or null when no exporter is installed |
A peering plus a Kvindo-side peer exposing an existing subnet.
Terraform
Python SDK
kc CLI
Resource docs
Examples
More in this section