Cloudeka Vpc

One of your private networks. A default VPC is created automatically when your namespace is set up. You can create additional VPCs yourself to segment workloads.

kubectl get cvpc -n <your-namespace>
kubectl get cvpc -n <your-namespace> -o yaml

Create one

apiVersion: tenants.cloudeka.ai/v1alpha2
kind: CloudekaVPC
metadata:
  name: my-second-network
  namespace: <your-namespace>
spec:
  isolate: true

kubectl apply -f my-vpc.yaml

Fields that matter to you

Field	Where	Meaning
spec.isolate	spec	true = no outbound internet (fully isolated); false = outbound NAT enabled
status.cidrBlock	status	Assigned CIDR range for this network, set after creation
status.gateway	status	Assigned gateway address
status.referenceID	status	Internal reference to the underlying network object — informational only

Good to know

• status.cidrBlock/status.gateway are populated after the VPC is provisioned — expect a short delay after kubectl apply before they appear.

• Deleting a CloudekaVPC tears down the underlying network cleanly, including any associated default network policy.

• To change spec.isolate after creation, kubectl edit/apply the change — it's reconciled automatically (no need to delete/recreate).

• See Networking for how this relates to Cloudeka Guard (network policy within a VPC).