Skip to main content
RouteTable represents a routing configuration for a VPC network. Each route table can be associated with multiple subnets and contains rules for routing traffic to different destinations.

​
Schema

​
Required

  • network_id (String) ID of the VPC network this route table belongs to.
  • parent_id (String) Identifier of the parent resource to which the resource belongs.

​
Optional

  • labels (Map of String) : Labels associated with the resource.
  • metadata (Attributes) : metadata.parent_id represents the Project.

    ​
    Inner value description

    Common resource metadata. (see below for nested schema)
  • name (String) Human readable name for the resource.

​
Read-Only

  • created_at (String) : Timestamp indicating when the resource was created. A string representing a timestamp in ISO 8601 format: YYYY-MM-DDTHH:MM:SSZ or YYYY-MM-DDTHH:MM:SS.SSS±HH:MM
  • id (String) Identifier for the resource, unique for its resource type.
  • resource_version (Number) : Version of the resource for safe concurrent modifications and consistent reads. Positive and monotonically increases on each resource spec change (but not on each change of the resource’s container(s) or status). Service allows zero value or current.
  • status (Attributes) Current status of the route table. (see below for nested schema)
  • updated_at (String) : Timestamp indicating when the resource was last updated. A string representing a timestamp in ISO 8601 format: YYYY-MM-DDTHH:MM:SSZ or YYYY-MM-DDTHH:MM:SS.SSS±HH:MM

​
Nested Schema for metadata

​
Nested Schema for status

Read-Only:
  • assignment (Attributes) Information about which subnets are using this route table. (see below for nested schema)
  • default (Boolean) : Indicates if this is the default route table for the network. Only one route table can be default per network.
  • state (String) : Current state of the route table.

    ​
    Supported values

    State indicates the current operational state of the route table. Possible values:
    • STATE_UNSPECIFIED - The state is unknown or not yet set.
    • READY - The route table is configured and operational.

​
Nested Schema for status.assignment

Read-Only:
  • subnets (List of String) List of subnet IDs that use this route table for their routing configuration.