Kvindo™ Cloud Docs
A basic private network: a VPC with a floating IP attached for outbound NAT, and a subnet. Attaching a floating IP to the VPC (nat_floating_ip_id) gives every resource in it outbound internet access — no separate NAT gateway. Every resource is placed in the organization's default folder, looked up with a datasource.
This assumes the provider is configured (see Getting started). Apply with terraform apply.
Creates two VPCs, each with its own subnet, and peers them via a VPC Peering with a Peering Peer gateway on each side. A Route Table in each direction lets a whole subnet — not just its own gateway VM — reach the other side, so any VM in subnet "a" can talk to any VM in subnet "b" and back.
Another self-contained example — its own VPC/subnet with one internal Peering
Peer, plus a VM standing in for whatever is on the other side, connected via an
External Peer instead of a second Peering Peer. Kvindo reaches an External
Peer over SSH directly, so it needs no floating IP of its own on the Kvindo side — only
ssh_ipv4/ssh_user/ssh_private_key_id/
private_ipv4 to reach whatever's actually on the other end. Paste your own SSH
key pair in place of the kvindo_ssh_key/kvindo_ssh_private_key
placeholders below and replace the VM with your real external network to use this for real. As
with Peering above, the Peering Peer plus its External Peer counterpart only wire up
connectivity for the peer's own gateway VM — a Route Table lets the rest of the own subnet
reach whatever's advertised on the other side too, resolved automatically by Terraform's own
dependency graph like the rest of this example.
Resource docs
More in this section
Reference