Kvindo™ Cloud Docs

Language
VPC Peering

A VPC Peering is a container that joins networks over private IPs. The peering itself carries only metadata — you attach the two sides as separate Peering Peer (Kvindo VPC) or External Peering Peer (a network outside Kvindo) resources that reference it.

Key concepts

• Peers — each side is a VpcPeeringPeer (a Kvindo subnet) or VpcPeeringExternalPeer (an external network) pointing at this peering

• Private routing — the peer's gateway (the internal peer's Floating IP-holding VM, or the external side's router) reaches the other side over private IPs; a Floating IP is required on every internal peer, and only that one gateway host gets connectivity automatically

• Non-overlapping CIDRs — the two sides must not share IP ranges

• Non-transitive — A↔B and B↔C does not imply A↔C

Creating a VPC Peering plus its Peer(s) only wires up automatic connectivity for the peer's own gateway — the VM holding the internal peer's Floating IP, or the external side's router host. For any other VM in the peered subnet to reach the far side, you must also add a Route Table + Route Table Route (destination = the peer's CIDR, target = the gateway's private IP) attached via a Route Table Attachment, and Security Group ingress rules on the destination VM allowing the peer's CIDR (the default is deny-all). See the worked example below.
Maintainer endpoint: Kvindo also runs a small maintainer daemon on every gateway host in the peering (the internal peer's VM and, for an external peer, the remote router), bound to its private IP on port 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).

A VPC peering has no spec of its own — only the common metadata below.

Parameters
This resource has no fields of its own — it uses only the common metadata and status fields. Switch the filter above to "All fields" to see them.
Examples

The peering container. Add peers with a Peering Peer / External Peering Peer that references it.

Terraform

Python SDK

kc CLI

Example: peering with routing

A peering plus a Kvindo-side peer, with the Route Table and Security Group needed so a whole subnet — not just the peer's own gateway VM — can reach the far side. Attach the Security Group's id to spec.securityGroupIds on whichever VM(s) should actually be reachable from the peer; creating it alone does nothing. 10.20.0.0/16 below is only an illustrative placeholder — replace it with whatever CIDR your actual peer advertises, it isn't a required or reserved value.

Terraform

Python SDK

kc CLI

Related pages

Resource docs

Examples

More in this section

Reference

An unhandled error has occurred. Reload 🗙