Kvindo™ Cloud Docs
A VPC (Virtual Private Cloud) is a logically isolated network within the cloud platform. All other network resources — subnets, route tables, security groups, NAT gateways — live inside a VPC.
• No VPC-level CIDR — a VPC has no address range of its own; the private IPv4 ranges live on its subnets, which each carry their own ipv4Cidr
• Hosting provider — the region/provider the VPC is created in; there is no default, so pass one explicitly (kc get provider lists the options)
• NAT floating IP — attach a Floating IP to give the whole VPC outbound internet access (source-NAT)
• Subnets — subdivisions of the VPC where VMs and other resources land
• Peering — connect resources across VPCs privately via VPC Peering
| UI Name | API / kc name | Terraform name | Optional | Format | Default | Is read only | Description |
|---|---|---|---|---|---|---|---|
| Hosting Provider | spec.hostingProviderId |
spec.hosting_provider_id |
Yes | ULID (nullable) — references a Hosting Provider | — | No | Region/provider the VPC is created in (a ULID, not a name); no default — run kc get provider for options |
| NAT Floating IP | spec.natFloatingIpId |
spec.nat_floating_ip_id |
Yes | ULID (nullable) — references a Floating IP | — | No | Floating IP used for source-NAT outbound internet access from the VPC |
| NAT Public IPv4 | status.natPublicIpV4 |
status.nat_public_ipv4 |
— | string (nullable) | — | Yes | Public IPv4 the VPC uses for outbound NAT |
Create one VPC per environment (development, staging, production) for strong network isolation. Give each VPC's subnets non-overlapping CIDRs so the VPCs can later be joined with VPC Peering without address clashes.
A VPC in the default region. Add subnets next — that is where the private IPv4 ranges are defined.
Terraform
Python SDK
kc CLI
Examples
More in this section