Update VPC Virtualization
Update network virtualization type for a VPC
Org must have a Tenant entity. User must have authorization role with TENANT_ADMIN suffix
Tenant must own the VPC Request is rejected if the VPC already has Subnets or Instances.
Authentication
export JWT_BEARER_TOKEN="<jwt-bearer-token>"
# Example org name: "acme-inc
export ORG_NAME=<org-name>
# Use the JWT bearer token in your API request auth header:
curl -v -X GET -H "Content-Type: application/json" -H "Authorization: Bearer $JWT_BEARER_TOKEN" https://nico-rest-api.nico.svc.cluster.local/v2/org/$ORG_NAME/nico/user/current
Path parameters
Request
Network virtualization type of the VPC. Can only be updated to FNN
Response
Network virtualization type of the VPC. Flat VPCs hold instances on zero-DPU hosts (or hosts with their DPU in NIC mode); their interfaces are bound to underlay (HostInband) network segments and NICo does not drive their data plane.
Whether this VPC uses SLAAC allocation mode for instance IPv6 interfaces. When true, Core allocates a /64 to each interface that includes IPv6 and retains the prefix without assigning a concrete IPv6 host address. This value is fixed when the VPC is created. The DPU sends router advertisements (RAs) on routed FNN interfaces. With SLAAC enabled, it sends them only when the interface prefix is exactly a /64.
Routing profile type for the VPC. Populated when Site has Native Networking enabled and network virtualization type is FNN.
Routing-profile properties set directly on the VPC. Unset properties inherit from the named routing profile.
String key-value pairs describing VPC labels
Date/time when VPC was created
Date/time when VPC was last updated