@robinmordasiewicz/f5xc-terraform-mcp 2.3.0 → 2.4.3

package/dist/docs/resources/gcp_vpc_site.md

@@ -0,0 +1,1170 @@
+---
+page_title: "f5xc_gcp_vpc_site Resource - terraform-provider-f5xc"
+subcategory: "Sites"
+description: |-
+  [Category: Sites] [Namespace: required] Manages a GCP VPC Site resource in F5 Distributed Cloud for deploying F5 sites within Google Cloud VPC environments.
+---
+
+# f5xc_gcp_vpc_site (Resource)
+
+[Category: Sites] [Namespace: required] Manages a GCP VPC Site resource in F5 Distributed Cloud for deploying F5 sites within Google Cloud VPC environments.
+
+~> **Note** Please refer to [GCP VPC Site API docs](https://docs.cloud.f5.com/docs-v2/api/views-gcp-vpc-site) to learn more.
+
+## Example Usage
+
+```terraform
+# GCP VPC Site Resource Example
+# [Category: Sites] [Namespace: required] Manages a GCP VPC Site resource in F5 Distributed Cloud for deploying F5 sites within Google Cloud VPC environments.
+
+# Basic GCP VPC Site configuration
+resource "f5xc_gcp_vpc_site" "example" {
+  name      = "example-gcp-vpc-site"
+  namespace = "system"
+
+  labels = {
+    environment = "production"
+    managed_by  = "terraform"
+  }
+
+  annotations = {
+    "owner" = "platform-team"
+  }
+
+  # GCP VPC Site configuration
+  gcp_region = "us-west1"
+
+  # GCP credentials reference
+  cloud_credentials {
+    name      = "gcp-credentials"
+    namespace = "system"
+  }
+
+  # Instance type
+  instance_type = "n1-standard-4"
+
+  # Ingress/Egress gateway
+  ingress_egress_gw {
+    gcp_certified_hw = "gcp-byol-multi-nic-voltmesh"
+    node_number      = 1
+    inside_network {
+      new_network {
+        name = "inside-network"
+      }
+    }
+    outside_network {
+      new_network {
+        name = "outside-network"
+      }
+    }
+    inside_subnet {
+      new_subnet {
+        subnet_name  = "inside-subnet"
+        primary_ipv4 = "10.0.1.0/24"
+      }
+    }
+    outside_subnet {
+      new_subnet {
+        subnet_name  = "outside-subnet"
+        primary_ipv4 = "10.0.2.0/24"
+      }
+    }
+  }
+
+  # No worker nodes by default
+  no_worker_nodes {}
+}
+```
+
+<!-- schema generated by tfplugindocs -->
+## Argument Reference
+
+### Metadata Argument Reference
+
+<a id="name"></a>&#x2022; [`name`](#name) - Required String<br>Name of the GCP VPC Site. Must be unique within the namespace
+
+<a id="namespace"></a>&#x2022; [`namespace`](#namespace) - Required String<br>Namespace where the GCP VPC Site will be created
+
+<a id="annotations"></a>&#x2022; [`annotations`](#annotations) - Optional Map<br>Annotations is an unstructured key value map stored with a resource that may be set by external tools to store and retrieve arbitrary metadata
+
+<a id="description"></a>&#x2022; [`description`](#description) - Optional String<br>Human readable description for the object
+
+<a id="disable"></a>&#x2022; [`disable`](#disable) - Optional Bool<br>A value of true will administratively disable the object
+
+<a id="labels"></a>&#x2022; [`labels`](#labels) - Optional Map<br>Labels is a user defined key value map that can be attached to resources for organization and filtering
+
+### Spec Argument Reference
+
+<a id="address"></a>&#x2022; [`address`](#address) - Optional String<br>Geographical Address. Site's geographical address that can be used to determine its latitude and longitude
+
+<a id="admin-password"></a>&#x2022; [`admin_password`](#admin-password) - Optional Block<br>Secret. SecretType is used in an object to indicate a sensitive/confidential field<br>See [Admin Password](#admin-password) below for details.
+
+-> **One of the following:**
+&#x2022; <a id="block-all-services"></a>[`block_all_services`](#block-all-services) - Optional Block<br>Enable this option
+<br><br>&#x2022; <a id="blocked-services"></a>[`blocked_services`](#blocked-services) - Optional Block<br>Disable Node Local Services. Disable node local services on this site. Note: The chosen services will get disabled on all nodes in the site<br>See [Blocked Services](#blocked-services) below for details.
+
+<a id="cloud-credentials"></a>&#x2022; [`cloud_credentials`](#cloud-credentials) - Optional Block<br>Object reference. This type establishes a direct reference from one object(the referrer) to another(the referred). Such a reference is in form of tenant/namespace/name<br>See [Cloud Credentials](#cloud-credentials) below for details.
+
+<a id="coordinates"></a>&#x2022; [`coordinates`](#coordinates) - Optional Block<br>Site Coordinates. Coordinates of the site which provides the site physical location<br>See [Coordinates](#coordinates) below for details.
+
+<a id="custom-dns"></a>&#x2022; [`custom_dns`](#custom-dns) - Optional Block<br>Custom DNS. Custom DNS is the configured for specify CE site<br>See [Custom DNS](#custom-dns) below for details.
+
+<a id="default-blocked-services"></a>&#x2022; [`default_blocked_services`](#default-blocked-services) - Optional Block<br>Enable this option
+
+<a id="disk-size"></a>&#x2022; [`disk_size`](#disk-size) - Optional Number<br>Cloud Disk Size. Disk size to be used for this instance in GiB. 80 is 80 GiB
+
+<a id="gcp-labels"></a>&#x2022; [`gcp_labels`](#gcp-labels) - Optional Block<br>GCP Labels. GCP Label is a label consisting of a user-defined key and value. It helps to manage, identify, organize, search for, and filter resources in GCP console
+
+<a id="gcp-region"></a>&#x2022; [`gcp_region`](#gcp-region) - Optional String<br>GCP Region. Name for GCP Region
+
+-> **One of the following:**
+&#x2022; <a id="ingress-egress-gw"></a>[`ingress_egress_gw`](#ingress-egress-gw) - Optional Block<br>GCP Ingress/Egress Gateway. Two interface GCP ingress/egress site<br>See [Ingress Egress Gw](#ingress-egress-gw) below for details.
+<br><br>&#x2022; <a id="ingress-gw"></a>[`ingress_gw`](#ingress-gw) - Optional Block<br>GCP Ingress Gateway. Single interface GCP ingress site
+<br><br>&#x2022; <a id="voltstack-cluster"></a>[`voltstack_cluster`](#voltstack-cluster) - Optional Block<br>GCP App Stack Cluster. App Stack cluster of single interface GCP site
+
+<a id="instance-type"></a>&#x2022; [`instance_type`](#instance-type) - Optional String<br>GCP Instance Type for Node. Select Instance size based on performance needed
+
+<a id="kubernetes-upgrade-drain"></a>&#x2022; [`kubernetes_upgrade_drain`](#kubernetes-upgrade-drain) - Optional Block<br>Node by Node Upgrade. Specify how worker nodes within a site will be upgraded
+
+-> **One of the following:**
+&#x2022; <a id="log-receiver"></a>[`log_receiver`](#log-receiver) - Optional Block<br>Object reference. This type establishes a direct reference from one object(the referrer) to another(the referred). Such a reference is in form of tenant/namespace/name
+<br><br>&#x2022; <a id="logs-streaming-disabled"></a>[`logs_streaming_disabled`](#logs-streaming-disabled) - Optional Block<br>Enable this option
+
+<a id="offline-survivability-mode"></a>&#x2022; [`offline_survivability_mode`](#offline-survivability-mode) - Optional Block<br>Offline Survivability Mode. Offline Survivability allows the Site to continue functioning normally without traffic loss during periods of connectivity loss to the Regional Edge (RE) or the Global Controller (GC). When this feature is enabled, a site can continue to function as is with existing configuration for upto 7 days, even when the site is offline. The certificates needed to keep the services running on this site are signed using a local CA. Secrets would also be cached locally to handle the connectivity loss. When the mode is toggled, services will restart and traffic disruption will be seen
+
+<a id="os"></a>&#x2022; [`os`](#os) - Optional Block<br>Operating System Version. Select the F5XC Operating System Version for the site. By default, latest available OS Version will be used. Refer to release notes to find required released OS versions
+
+-> **One of the following:**
+&#x2022; <a id="private-connect-disabled"></a>[`private_connect_disabled`](#private-connect-disabled) - Optional Block<br>Enable this option
+<br><br>&#x2022; <a id="private-connectivity"></a>[`private_connectivity`](#private-connectivity) - Optional Block<br>Private Connect Configuration. Private Connect Configuration
+
+<a id="ssh-key"></a>&#x2022; [`ssh_key`](#ssh-key) - Optional String<br>Public SSH key. Public SSH key for accessing the site
+
+<a id="sw"></a>&#x2022; [`sw`](#sw) - Optional Block<br>F5XC Software Version. Select the F5XC Software Version for the site. By default, latest available F5XC Software Version will be used. Refer to release notes to find required released SW versions
+
+<a id="timeouts"></a>&#x2022; [`timeouts`](#timeouts) - Optional Block
+
+### Attributes Reference
+
+In addition to all arguments above, the following attributes are exported:
+
+<a id="id"></a>&#x2022; [`id`](#id) - Optional String<br>Unique identifier for the resource
+
+---
+
+#### Admin Password
+
+An [`admin_password`](#admin-password) block supports the following:
+
+<a id="admin-password-blindfold-secret-info"></a>&#x2022; [`blindfold_secret_info`](#admin-password-blindfold-secret-info) - Optional Block<br>Blindfold Secret. BlindfoldSecretInfoType specifies information about the Secret managed by F5XC Secret Management<br>See [Blindfold Secret Info](#admin-password-blindfold-secret-info) below.
+
+<a id="admin-password-clear-secret-info"></a>&#x2022; [`clear_secret_info`](#admin-password-clear-secret-info) - Optional Block<br>In-Clear Secret. ClearSecretInfoType specifies information about the Secret that is not encrypted<br>See [Clear Secret Info](#admin-password-clear-secret-info) below.
+
+#### Admin Password Blindfold Secret Info
+
+A [`blindfold_secret_info`](#admin-password-blindfold-secret-info) block (within [`admin_password`](#admin-password)) supports the following:
+
+<a id="admin-password-blindfold-secret-info-decryption-provider"></a>&#x2022; [`decryption_provider`](#admin-password-blindfold-secret-info-decryption-provider) - Optional String<br>Decryption Provider. Name of the Secret Management Access object that contains information about the backend Secret Management service
+
+<a id="admin-password-blindfold-secret-info-location"></a>&#x2022; [`location`](#admin-password-blindfold-secret-info-location) - Optional String<br>Location. Location is the uri_ref. It could be in URL format for string:/// Or it could be a path if the store provider is an HTTP/HTTPS location
+
+<a id="admin-password-blindfold-secret-info-store-provider"></a>&#x2022; [`store_provider`](#admin-password-blindfold-secret-info-store-provider) - Optional String<br>Store Provider. Name of the Secret Management Access object that contains information about the store to get encrypted bytes This field needs to be provided only if the URL scheme is not string:///
+
+#### Admin Password Clear Secret Info
+
+A [`clear_secret_info`](#admin-password-clear-secret-info) block (within [`admin_password`](#admin-password)) supports the following:
+
+<a id="admin-password-clear-secret-info-provider-ref"></a>&#x2022; [`provider_ref`](#admin-password-clear-secret-info-provider-ref) - Optional String<br>Provider. Name of the Secret Management Access object that contains information about the store to get encrypted bytes This field needs to be provided only if the URL scheme is not string:///
+
+<a id="admin-password-clear-secret-info-url"></a>&#x2022; [`url`](#admin-password-clear-secret-info-url) - Optional String<br>URL. URL of the secret. Currently supported URL schemes is string:///. For string:/// scheme, Secret needs to be encoded Base64 format. When asked for this secret, caller will get Secret bytes after Base64 decoding
+
+#### Blocked Services
+
+A [`blocked_services`](#blocked-services) block supports the following:
+
+<a id="blocked-services-blocked-sevice"></a>&#x2022; [`blocked_sevice`](#blocked-services-blocked-sevice) - Optional Block<br>Disable Node Local Services<br>See [Blocked Sevice](#blocked-services-blocked-sevice) below.
+
+#### Blocked Services Blocked Sevice
+
+A [`blocked_sevice`](#blocked-services-blocked-sevice) block (within [`blocked_services`](#blocked-services)) supports the following:
+
+<a id="blocked-services-blocked-sevice-dns"></a>&#x2022; [`dns`](#blocked-services-blocked-sevice-dns) - Optional Block<br>Enable this option
+
+<a id="blocked-services-blocked-sevice-network-type"></a>&#x2022; [`network_type`](#blocked-services-blocked-sevice-network-type) - Optional String  Defaults to `VIRTUAL_NETWORK_SITE_LOCAL`<br>Possible values are `VIRTUAL_NETWORK_SITE_LOCAL`, `VIRTUAL_NETWORK_SITE_LOCAL_INSIDE`, `VIRTUAL_NETWORK_PER_SITE`, `VIRTUAL_NETWORK_PUBLIC`, `VIRTUAL_NETWORK_GLOBAL`, `VIRTUAL_NETWORK_SITE_SERVICE`, `VIRTUAL_NETWORK_VER_INTERNAL`, `VIRTUAL_NETWORK_SITE_LOCAL_INSIDE_OUTSIDE`, `VIRTUAL_NETWORK_IP_AUTO`, `VIRTUAL_NETWORK_VOLTADN_PRIVATE_NETWORK`, `VIRTUAL_NETWORK_SRV6_NETWORK`, `VIRTUAL_NETWORK_IP_FABRIC`, `VIRTUAL_NETWORK_SEGMENT`<br>[Enum: VIRTUAL_NETWORK_SITE_LOCAL|VIRTUAL_NETWORK_SITE_LOCAL_INSIDE|VIRTUAL_NETWORK_PER_SITE|VIRTUAL_NETWORK_PUBLIC|VIRTUAL_NETWORK_GLOBAL|VIRTUAL_NETWORK_SITE_SERVICE|VIRTUAL_NETWORK_VER_INTERNAL|VIRTUAL_NETWORK_SITE_LOCAL_INSIDE_OUTSIDE|VIRTUAL_NETWORK_IP_AUTO|VIRTUAL_NETWORK_VOLTADN_PRIVATE_NETWORK|VIRTUAL_NETWORK_SRV6_NETWORK|VIRTUAL_NETWORK_IP_FABRIC|VIRTUAL_NETWORK_SEGMENT] Virtual Network Type. Different types of virtual networks understood by the system Virtual-network of type VIRTUAL_NETWORK_SITE_LOCAL provides connectivity to public (outside) network. This is an insecure network and is connected to public internet via NAT Gateways/firwalls Virtual-network of this type is local to every site. Two virtual networks of this type on different sites are neither related nor connected. Constraints: There can be atmost one virtual network of this type in a given site. This network type is supported on CE sites. This network is created automatically and present on all sites Virtual-network of type VIRTUAL_NETWORK_SITE_LOCAL_INSIDE is a private network inside site. It is a secure network and is not connected to public network. Virtual-network of this type is local to every site. Two virtual networks of this type on different sites are neither related nor connected. Constraints: There can be atmost one virtual network of this type in a given site. This network type is supported on CE sites. This network is created during provisioning of site User defined per-site virtual network. Scope of this virtual network is limited to the site. This is not yet supported Virtual-network of type VIRTUAL_NETWORK_PUBLIC directly conects to the public internet. Virtual-network of this type is local to every site. Two virtual networks of this type on different sites are neither related nor connected. Constraints: There can be atmost one virtual network of this type in a given site. This network type is supported on RE sites only It is an internally created by the system. They must not be created by user Virtual Neworks with global scope across different sites in F5XC domain. An example global virtual-network called 'AIN Network' is created for every tenant. for volterra fabric Constraints: It is currently only supported as internally created by the system. vK8s service network for a given tenant. Used to advertise a virtual host only to vk8s pods for that tenant Constraints: It is an internally created by the system. Must not be created by user VER internal network for the site. It can only be used for virtual hosts with SMA_PROXY type proxy Constraints: It is an internally created by the system. Must not be created by user Virtual-network of type VIRTUAL_NETWORK_SITE_LOCAL_INSIDE_OUTSIDE represents both VIRTUAL_NETWORK_SITE_LOCAL and VIRTUAL_NETWORK_SITE_LOCAL_INSIDE Constraints: This network type is only meaningful in an advertise policy When virtual-network of type VIRTUAL_NETWORK_IP_AUTO is selected for an endpoint, VER will try to determine the network based on the provided IP address Constraints: This network type is only meaningful in an endpoint VoltADN Private Network is used on volterra RE(s) to connect to customer private networks This network is created by opening a support ticket This network is per site srv6 network VER IP Fabric network for the site. This Virtual network type is used for exposing virtual host on IP Fabric network on the VER site or for endpoint in IP Fabric network Constraints: It is an internally created by the system. Must not be created by user Network internally created for a segment Constraints: It is an internally created by the system. Must not be created by user
+
+<a id="blocked-services-blocked-sevice-ssh"></a>&#x2022; [`ssh`](#blocked-services-blocked-sevice-ssh) - Optional Block<br>Enable this option
+
+<a id="blocked-services-blocked-sevice-web-user-interface"></a>&#x2022; [`web_user_interface`](#blocked-services-blocked-sevice-web-user-interface) - Optional Block<br>Enable this option
+
+#### Cloud Credentials
+
+A [`cloud_credentials`](#cloud-credentials) block supports the following:
+
+<a id="cloud-credentials-name"></a>&#x2022; [`name`](#cloud-credentials-name) - Optional String<br>Name. When a configuration object(e.g. virtual_host) refers to another(e.g route) then name will hold the referred object's(e.g. route's) name
+
+<a id="cloud-credentials-namespace"></a>&#x2022; [`namespace`](#cloud-credentials-namespace) - Optional String<br>Namespace. When a configuration object(e.g. virtual_host) refers to another(e.g route) then namespace will hold the referred object's(e.g. route's) namespace
+
+<a id="cloud-credentials-tenant"></a>&#x2022; [`tenant`](#cloud-credentials-tenant) - Optional String<br>Tenant. When a configuration object(e.g. virtual_host) refers to another(e.g route) then tenant will hold the referred object's(e.g. route's) tenant
+
+#### Coordinates
+
+A [`coordinates`](#coordinates) block supports the following:
+
+<a id="coordinates-latitude"></a>&#x2022; [`latitude`](#coordinates-latitude) - Optional Number<br>Latitude. Latitude of the site location
+
+<a id="coordinates-longitude"></a>&#x2022; [`longitude`](#coordinates-longitude) - Optional Number<br>Longitude. longitude of site location
+
+#### Custom DNS
+
+A [`custom_dns`](#custom-dns) block supports the following:
+
+<a id="custom-dns-inside-nameserver"></a>&#x2022; [`inside_nameserver`](#custom-dns-inside-nameserver) - Optional String<br>DNS Server for Inside Network. Optional DNS server IP to be used for name resolution in inside network
+
+<a id="custom-dns-outside-nameserver"></a>&#x2022; [`outside_nameserver`](#custom-dns-outside-nameserver) - Optional String<br>DNS Server for Outside Network. Optional DNS server IP to be used for name resolution in outside network
+
+#### Ingress Egress Gw
+
+An [`ingress_egress_gw`](#ingress-egress-gw) block supports the following:
+
+<a id="ingress-egress-gw-active-enhanced-firewall-policies"></a>&#x2022; [`active_enhanced_firewall_policies`](#ingress-egress-gw-active-enhanced-firewall-policies) - Optional Block<br>Active Enhanced Network Policies Type. List of Enhanced Firewall Policies These policies use session-based rules and provide all options available under firewall policies with an additional option for service insertion<br>See [Active Enhanced Firewall Policies](#ingress-egress-gw-active-enhanced-firewall-policies) below.
+
+<a id="ingress-egress-gw-active-forward-proxy-policies"></a>&#x2022; [`active_forward_proxy_policies`](#ingress-egress-gw-active-forward-proxy-policies) - Optional Block<br>Active Forward Proxy Policies Type. Ordered List of Forward Proxy Policies active<br>See [Active Forward Proxy Policies](#ingress-egress-gw-active-forward-proxy-policies) below.
+
+<a id="ingress-egress-gw-active-network-policies"></a>&#x2022; [`active_network_policies`](#ingress-egress-gw-active-network-policies) - Optional Block<br>Active Firewall Policies Type. List of firewall policy views<br>See [Active Network Policies](#ingress-egress-gw-active-network-policies) below.
+
+<a id="ingress-egress-gw-dc-cluster-group-inside-vn"></a>&#x2022; [`dc_cluster_group_inside_vn`](#ingress-egress-gw-dc-cluster-group-inside-vn) - Optional Block<br>Object reference. This type establishes a direct reference from one object(the referrer) to another(the referred). Such a reference is in form of tenant/namespace/name<br>See [Dc Cluster Group Inside Vn](#ingress-egress-gw-dc-cluster-group-inside-vn) below.
+
+<a id="ingress-egress-gw-dc-cluster-group-outside-vn"></a>&#x2022; [`dc_cluster_group_outside_vn`](#ingress-egress-gw-dc-cluster-group-outside-vn) - Optional Block<br>Object reference. This type establishes a direct reference from one object(the referrer) to another(the referred). Such a reference is in form of tenant/namespace/name<br>See [Dc Cluster Group Outside Vn](#ingress-egress-gw-dc-cluster-group-outside-vn) below.
+
+<a id="ingress-egress-gw-forward-proxy-allow-all"></a>&#x2022; [`forward_proxy_allow_all`](#ingress-egress-gw-forward-proxy-allow-all) - Optional Block<br>Enable this option
+
+<a id="ingress-egress-gw-gcp-certified-hw"></a>&#x2022; [`gcp_certified_hw`](#ingress-egress-gw-gcp-certified-hw) - Optional String<br>GCP Certified Hardware. Name for GCP certified hardware
+
+<a id="ingress-egress-gw-gcp-zone-names"></a>&#x2022; [`gcp_zone_names`](#ingress-egress-gw-gcp-zone-names) - Optional List<br>GCP zone names.List of zones when instances will be created, needs to match with region selected
+
+<a id="ingress-egress-gw-global-network-list"></a>&#x2022; [`global_network_list`](#ingress-egress-gw-global-network-list) - Optional Block<br>Global Network Connection List. List of global network connections<br>See [Global Network List](#ingress-egress-gw-global-network-list) below.
+
+<a id="ingress-egress-gw-inside-network"></a>&#x2022; [`inside_network`](#ingress-egress-gw-inside-network) - Optional Block<br>GCP VPC network choice. This defines choice about GCP VPC network for a view<br>See [Inside Network](#ingress-egress-gw-inside-network) below.
+
+<a id="ingress-egress-gw-inside-static-routes"></a>&#x2022; [`inside_static_routes`](#ingress-egress-gw-inside-static-routes) - Optional Block<br>Static Route List Type. List of static routes<br>See [Inside Static Routes](#ingress-egress-gw-inside-static-routes) below.
+
+<a id="ingress-egress-gw-inside-subnet"></a>&#x2022; [`inside_subnet`](#ingress-egress-gw-inside-subnet) - Optional Block<br>GCP VPC network choice. This defines choice about GCP VPC network for a view<br>See [Inside Subnet](#ingress-egress-gw-inside-subnet) below.
+
+<a id="ingress-egress-gw-no-dc-cluster-group"></a>&#x2022; [`no_dc_cluster_group`](#ingress-egress-gw-no-dc-cluster-group) - Optional Block<br>Enable this option
+
+<a id="ingress-egress-gw-no-forward-proxy"></a>&#x2022; [`no_forward_proxy`](#ingress-egress-gw-no-forward-proxy) - Optional Block<br>Enable this option
+
+<a id="ingress-egress-gw-no-global-network"></a>&#x2022; [`no_global_network`](#ingress-egress-gw-no-global-network) - Optional Block<br>Enable this option
+
+<a id="ingress-egress-gw-no-inside-static-routes"></a>&#x2022; [`no_inside_static_routes`](#ingress-egress-gw-no-inside-static-routes) - Optional Block<br>Enable this option
+
+<a id="ingress-egress-gw-no-network-policy"></a>&#x2022; [`no_network_policy`](#ingress-egress-gw-no-network-policy) - Optional Block<br>Enable this option
+
+<a id="ingress-egress-gw-no-outside-static-routes"></a>&#x2022; [`no_outside_static_routes`](#ingress-egress-gw-no-outside-static-routes) - Optional Block<br>Enable this option
+
+<a id="ingress-egress-gw-node-number"></a>&#x2022; [`node_number`](#ingress-egress-gw-node-number) - Optional Number<br>Number of main nodes. Number of main nodes to create, either 1 or 3
+
+<a id="ingress-egress-gw-outside-network"></a>&#x2022; [`outside_network`](#ingress-egress-gw-outside-network) - Optional Block<br>GCP VPC network choice. This defines choice about GCP VPC network for a view<br>See [Outside Network](#ingress-egress-gw-outside-network) below.
+
+<a id="ingress-egress-gw-outside-static-routes"></a>&#x2022; [`outside_static_routes`](#ingress-egress-gw-outside-static-routes) - Optional Block<br>Static Route List Type. List of static routes<br>See [Outside Static Routes](#ingress-egress-gw-outside-static-routes) below.
+
+<a id="ingress-egress-gw-outside-subnet"></a>&#x2022; [`outside_subnet`](#ingress-egress-gw-outside-subnet) - Optional Block<br>GCP VPC network choice. This defines choice about GCP VPC network for a view<br>See [Outside Subnet](#ingress-egress-gw-outside-subnet) below.
+
+<a id="ingress-egress-gw-performance-enhancement-mode"></a>&#x2022; [`performance_enhancement_mode`](#ingress-egress-gw-performance-enhancement-mode) - Optional Block<br>Performance Enhancement Mode.Optimize the site for L3 or L7 traffic processing. L7 optimized is the default<br>See [Performance Enhancement Mode](#ingress-egress-gw-performance-enhancement-mode) below.
+
+<a id="ingress-egress-gw-sm-connection-public-ip"></a>&#x2022; [`sm_connection_public_ip`](#ingress-egress-gw-sm-connection-public-ip) - Optional Block<br>Enable this option
+
+<a id="ingress-egress-gw-sm-connection-pvt-ip"></a>&#x2022; [`sm_connection_pvt_ip`](#ingress-egress-gw-sm-connection-pvt-ip) - Optional Block<br>Enable this option
+
+#### Ingress Egress Gw Active Enhanced Firewall Policies
+
+An [`active_enhanced_firewall_policies`](#ingress-egress-gw-active-enhanced-firewall-policies) block (within [`ingress_egress_gw`](#ingress-egress-gw)) supports the following:
+
+<a id="ingress-egress-gw-active-enhanced-firewall-policies-enhanced-firewall-policies"></a>&#x2022; [`enhanced_firewall_policies`](#ingress-egress-gw-active-enhanced-firewall-policies-enhanced-firewall-policies) - Optional Block<br>Enhanced Firewall Policy. Ordered List of Enhanced Firewall Policies active<br>See [Enhanced Firewall Policies](#ingress-egress-gw-active-enhanced-firewall-policies-enhanced-firewall-policies) below.
+
+#### Ingress Egress Gw Active Enhanced Firewall Policies Enhanced Firewall Policies
+
+An [`enhanced_firewall_policies`](#ingress-egress-gw-active-enhanced-firewall-policies-enhanced-firewall-policies) block (within [`ingress_egress_gw.active_enhanced_firewall_policies`](#ingress-egress-gw-active-enhanced-firewall-policies)) supports the following:
+
+<a id="ingress-egress-gw-active-enhanced-firewall-policies-enhanced-firewall-policies-name"></a>&#x2022; [`name`](#ingress-egress-gw-active-enhanced-firewall-policies-enhanced-firewall-policies-name) - Optional String<br>Name. When a configuration object(e.g. virtual_host) refers to another(e.g route) then name will hold the referred object's(e.g. route's) name
+
+<a id="ingress-egress-gw-active-enhanced-firewall-policies-enhanced-firewall-policies-namespace"></a>&#x2022; [`namespace`](#ingress-egress-gw-active-enhanced-firewall-policies-enhanced-firewall-policies-namespace) - Optional String<br>Namespace. When a configuration object(e.g. virtual_host) refers to another(e.g route) then namespace will hold the referred object's(e.g. route's) namespace
+
+<a id="ingress-egress-gw-active-enhanced-firewall-policies-enhanced-firewall-policies-tenant"></a>&#x2022; [`tenant`](#ingress-egress-gw-active-enhanced-firewall-policies-enhanced-firewall-policies-tenant) - Optional String<br>Tenant. When a configuration object(e.g. virtual_host) refers to another(e.g route) then tenant will hold the referred object's(e.g. route's) tenant
+
+#### Ingress Egress Gw Active Forward Proxy Policies
+
+An [`active_forward_proxy_policies`](#ingress-egress-gw-active-forward-proxy-policies) block (within [`ingress_egress_gw`](#ingress-egress-gw)) supports the following:
+
+<a id="ingress-egress-gw-active-forward-proxy-policies-forward-proxy-policies"></a>&#x2022; [`forward_proxy_policies`](#ingress-egress-gw-active-forward-proxy-policies-forward-proxy-policies) - Optional Block<br>Forward Proxy Policies. Ordered List of Forward Proxy Policies active<br>See [Forward Proxy Policies](#ingress-egress-gw-active-forward-proxy-policies-forward-proxy-policies) below.
+
+#### Ingress Egress Gw Active Forward Proxy Policies Forward Proxy Policies
+
+A [`forward_proxy_policies`](#ingress-egress-gw-active-forward-proxy-policies-forward-proxy-policies) block (within [`ingress_egress_gw.active_forward_proxy_policies`](#ingress-egress-gw-active-forward-proxy-policies)) supports the following:
+
+<a id="ingress-egress-gw-active-forward-proxy-policies-forward-proxy-policies-name"></a>&#x2022; [`name`](#ingress-egress-gw-active-forward-proxy-policies-forward-proxy-policies-name) - Optional String<br>Name. When a configuration object(e.g. virtual_host) refers to another(e.g route) then name will hold the referred object's(e.g. route's) name
+
+<a id="ingress-egress-gw-active-forward-proxy-policies-forward-proxy-policies-namespace"></a>&#x2022; [`namespace`](#ingress-egress-gw-active-forward-proxy-policies-forward-proxy-policies-namespace) - Optional String<br>Namespace. When a configuration object(e.g. virtual_host) refers to another(e.g route) then namespace will hold the referred object's(e.g. route's) namespace
+
+<a id="ingress-egress-gw-active-forward-proxy-policies-forward-proxy-policies-tenant"></a>&#x2022; [`tenant`](#ingress-egress-gw-active-forward-proxy-policies-forward-proxy-policies-tenant) - Optional String<br>Tenant. When a configuration object(e.g. virtual_host) refers to another(e.g route) then tenant will hold the referred object's(e.g. route's) tenant
+
+#### Ingress Egress Gw Active Network Policies
+
+An [`active_network_policies`](#ingress-egress-gw-active-network-policies) block (within [`ingress_egress_gw`](#ingress-egress-gw)) supports the following:
+
+<a id="ingress-egress-gw-active-network-policies-network-policies"></a>&#x2022; [`network_policies`](#ingress-egress-gw-active-network-policies-network-policies) - Optional Block<br>Firewall Policy. Ordered List of Firewall Policies active for this network firewall<br>See [Network Policies](#ingress-egress-gw-active-network-policies-network-policies) below.
+
+#### Ingress Egress Gw Active Network Policies Network Policies
+
+A [`network_policies`](#ingress-egress-gw-active-network-policies-network-policies) block (within [`ingress_egress_gw.active_network_policies`](#ingress-egress-gw-active-network-policies)) supports the following:
+
+<a id="ingress-egress-gw-active-network-policies-network-policies-name"></a>&#x2022; [`name`](#ingress-egress-gw-active-network-policies-network-policies-name) - Optional String<br>Name. When a configuration object(e.g. virtual_host) refers to another(e.g route) then name will hold the referred object's(e.g. route's) name
+
+<a id="ingress-egress-gw-active-network-policies-network-policies-namespace"></a>&#x2022; [`namespace`](#ingress-egress-gw-active-network-policies-network-policies-namespace) - Optional String<br>Namespace. When a configuration object(e.g. virtual_host) refers to another(e.g route) then namespace will hold the referred object's(e.g. route's) namespace
+
+<a id="ingress-egress-gw-active-network-policies-network-policies-tenant"></a>&#x2022; [`tenant`](#ingress-egress-gw-active-network-policies-network-policies-tenant) - Optional String<br>Tenant. When a configuration object(e.g. virtual_host) refers to another(e.g route) then tenant will hold the referred object's(e.g. route's) tenant
+
+#### Ingress Egress Gw Dc Cluster Group Inside Vn
+
+A [`dc_cluster_group_inside_vn`](#ingress-egress-gw-dc-cluster-group-inside-vn) block (within [`ingress_egress_gw`](#ingress-egress-gw)) supports the following:
+
+<a id="ingress-egress-gw-dc-cluster-group-inside-vn-name"></a>&#x2022; [`name`](#ingress-egress-gw-dc-cluster-group-inside-vn-name) - Optional String<br>Name. When a configuration object(e.g. virtual_host) refers to another(e.g route) then name will hold the referred object's(e.g. route's) name
+
+<a id="ingress-egress-gw-dc-cluster-group-inside-vn-namespace"></a>&#x2022; [`namespace`](#ingress-egress-gw-dc-cluster-group-inside-vn-namespace) - Optional String<br>Namespace. When a configuration object(e.g. virtual_host) refers to another(e.g route) then namespace will hold the referred object's(e.g. route's) namespace
+
+<a id="ingress-egress-gw-dc-cluster-group-inside-vn-tenant"></a>&#x2022; [`tenant`](#ingress-egress-gw-dc-cluster-group-inside-vn-tenant) - Optional String<br>Tenant. When a configuration object(e.g. virtual_host) refers to another(e.g route) then tenant will hold the referred object's(e.g. route's) tenant
+
+#### Ingress Egress Gw Dc Cluster Group Outside Vn
+
+A [`dc_cluster_group_outside_vn`](#ingress-egress-gw-dc-cluster-group-outside-vn) block (within [`ingress_egress_gw`](#ingress-egress-gw)) supports the following:
+
+<a id="ingress-egress-gw-dc-cluster-group-outside-vn-name"></a>&#x2022; [`name`](#ingress-egress-gw-dc-cluster-group-outside-vn-name) - Optional String<br>Name. When a configuration object(e.g. virtual_host) refers to another(e.g route) then name will hold the referred object's(e.g. route's) name
+
+<a id="ingress-egress-gw-dc-cluster-group-outside-vn-namespace"></a>&#x2022; [`namespace`](#ingress-egress-gw-dc-cluster-group-outside-vn-namespace) - Optional String<br>Namespace. When a configuration object(e.g. virtual_host) refers to another(e.g route) then namespace will hold the referred object's(e.g. route's) namespace
+
+<a id="ingress-egress-gw-dc-cluster-group-outside-vn-tenant"></a>&#x2022; [`tenant`](#ingress-egress-gw-dc-cluster-group-outside-vn-tenant) - Optional String<br>Tenant. When a configuration object(e.g. virtual_host) refers to another(e.g route) then tenant will hold the referred object's(e.g. route's) tenant
+
+#### Ingress Egress Gw Global Network List
+
+A [`global_network_list`](#ingress-egress-gw-global-network-list) block (within [`ingress_egress_gw`](#ingress-egress-gw)) supports the following:
+
+<a id="ingress-egress-gw-global-network-list-global-network-connections"></a>&#x2022; [`global_network_connections`](#ingress-egress-gw-global-network-list-global-network-connections) - Optional Block<br>Global Network Connections. Global network connections<br>See [Global Network Connections](#ingress-egress-gw-global-network-list-global-network-connections) below.
+
+#### Ingress Egress Gw Global Network List Global Network Connections
+
+A [`global_network_connections`](#ingress-egress-gw-global-network-list-global-network-connections) block (within [`ingress_egress_gw.global_network_list`](#ingress-egress-gw-global-network-list)) supports the following:
+
+<a id="ingress-egress-gw-global-network-list-global-network-connections-sli-to-global-dr"></a>&#x2022; [`sli_to_global_dr`](#ingress-egress-gw-global-network-list-global-network-connections-sli-to-global-dr) - Optional Block<br>Global Network. Global network reference for direct connection<br>See [SLI To Global DR](#ingress-egress-gw-global-network-list-global-network-connections-sli-to-global-dr) below.
+
+<a id="ingress-egress-gw-global-network-list-global-network-connections-slo-to-global-dr"></a>&#x2022; [`slo_to_global_dr`](#ingress-egress-gw-global-network-list-global-network-connections-slo-to-global-dr) - Optional Block<br>Global Network. Global network reference for direct connection<br>See [Slo To Global DR](#ingress-egress-gw-global-network-list-global-network-connections-slo-to-global-dr) below.
+
+#### Ingress Egress Gw Global Network List Global Network Connections SLI To Global DR
+
+A [`sli_to_global_dr`](#ingress-egress-gw-global-network-list-global-network-connections-sli-to-global-dr) block (within [`ingress_egress_gw.global_network_list.global_network_connections`](#ingress-egress-gw-global-network-list-global-network-connections)) supports the following:
+
+<a id="ingress-egress-gw-global-network-list-global-network-connections-sli-to-global-dr-global-vn"></a>&#x2022; [`global_vn`](#ingress-egress-gw-global-network-list-global-network-connections-sli-to-global-dr-global-vn) - Optional Block<br>Object reference. This type establishes a direct reference from one object(the referrer) to another(the referred). Such a reference is in form of tenant/namespace/name<br>See [Global Vn](#ingress-egress-gw-global-network-list-global-network-connections-sli-to-global-dr-global-vn) below.
+
+#### Ingress Egress Gw Global Network List Global Network Connections SLI To Global DR Global Vn
+
+A [`global_vn`](#ingress-egress-gw-global-network-list-global-network-connections-sli-to-global-dr-global-vn) block (within [`ingress_egress_gw.global_network_list.global_network_connections.sli_to_global_dr`](#ingress-egress-gw-global-network-list-global-network-connections-sli-to-global-dr)) supports the following:
+
+<a id="ingress-egress-gw-global-network-list-global-network-connections-sli-to-global-dr-global-vn-name"></a>&#x2022; [`name`](#ingress-egress-gw-global-network-list-global-network-connections-sli-to-global-dr-global-vn-name) - Optional String<br>Name. When a configuration object(e.g. virtual_host) refers to another(e.g route) then name will hold the referred object's(e.g. route's) name
+
+<a id="ingress-egress-gw-global-network-list-global-network-connections-sli-to-global-dr-global-vn-namespace"></a>&#x2022; [`namespace`](#ingress-egress-gw-global-network-list-global-network-connections-sli-to-global-dr-global-vn-namespace) - Optional String<br>Namespace. When a configuration object(e.g. virtual_host) refers to another(e.g route) then namespace will hold the referred object's(e.g. route's) namespace
+
+<a id="ingress-egress-gw-global-network-list-global-network-connections-sli-to-global-dr-global-vn-tenant"></a>&#x2022; [`tenant`](#ingress-egress-gw-global-network-list-global-network-connections-sli-to-global-dr-global-vn-tenant) - Optional String<br>Tenant. When a configuration object(e.g. virtual_host) refers to another(e.g route) then tenant will hold the referred object's(e.g. route's) tenant
+
+#### Ingress Egress Gw Global Network List Global Network Connections Slo To Global DR
+
+A [`slo_to_global_dr`](#ingress-egress-gw-global-network-list-global-network-connections-slo-to-global-dr) block (within [`ingress_egress_gw.global_network_list.global_network_connections`](#ingress-egress-gw-global-network-list-global-network-connections)) supports the following:
+
+<a id="ingress-egress-gw-global-network-list-global-network-connections-slo-to-global-dr-global-vn"></a>&#x2022; [`global_vn`](#ingress-egress-gw-global-network-list-global-network-connections-slo-to-global-dr-global-vn) - Optional Block<br>Object reference. This type establishes a direct reference from one object(the referrer) to another(the referred). Such a reference is in form of tenant/namespace/name<br>See [Global Vn](#ingress-egress-gw-global-network-list-global-network-connections-slo-to-global-dr-global-vn) below.
+
+#### Ingress Egress Gw Global Network List Global Network Connections Slo To Global DR Global Vn
+
+A [`global_vn`](#ingress-egress-gw-global-network-list-global-network-connections-slo-to-global-dr-global-vn) block (within [`ingress_egress_gw.global_network_list.global_network_connections.slo_to_global_dr`](#ingress-egress-gw-global-network-list-global-network-connections-slo-to-global-dr)) supports the following:
+
+<a id="ingress-egress-gw-global-network-list-global-network-connections-slo-to-global-dr-global-vn-name"></a>&#x2022; [`name`](#ingress-egress-gw-global-network-list-global-network-connections-slo-to-global-dr-global-vn-name) - Optional String<br>Name. When a configuration object(e.g. virtual_host) refers to another(e.g route) then name will hold the referred object's(e.g. route's) name
+
+<a id="ingress-egress-gw-global-network-list-global-network-connections-slo-to-global-dr-global-vn-namespace"></a>&#x2022; [`namespace`](#ingress-egress-gw-global-network-list-global-network-connections-slo-to-global-dr-global-vn-namespace) - Optional String<br>Namespace. When a configuration object(e.g. virtual_host) refers to another(e.g route) then namespace will hold the referred object's(e.g. route's) namespace
+
+<a id="ingress-egress-gw-global-network-list-global-network-connections-slo-to-global-dr-global-vn-tenant"></a>&#x2022; [`tenant`](#ingress-egress-gw-global-network-list-global-network-connections-slo-to-global-dr-global-vn-tenant) - Optional String<br>Tenant. When a configuration object(e.g. virtual_host) refers to another(e.g route) then tenant will hold the referred object's(e.g. route's) tenant
+
+#### Ingress Egress Gw Inside Network
+
+An [`inside_network`](#ingress-egress-gw-inside-network) block (within [`ingress_egress_gw`](#ingress-egress-gw)) supports the following:
+
+<a id="ingress-egress-gw-inside-network-existing-network"></a>&#x2022; [`existing_network`](#ingress-egress-gw-inside-network-existing-network) - Optional Block<br>GCP existing VPC network Type. Name of existing VPC network<br>See [Existing Network](#ingress-egress-gw-inside-network-existing-network) below.
+
+<a id="ingress-egress-gw-inside-network-new-network"></a>&#x2022; [`new_network`](#ingress-egress-gw-inside-network-new-network) - Optional Block<br>GCP VPC Network Manual Parameters. Parameters to create a new GCP VPC Network<br>See [New Network](#ingress-egress-gw-inside-network-new-network) below.
+
+<a id="ingress-egress-gw-inside-network-new-network-autogenerate"></a>&#x2022; [`new_network_autogenerate`](#ingress-egress-gw-inside-network-new-network-autogenerate) - Optional Block<br>GCP VPC Network Autogenerated Parameters. Create a new GCP VPC Network with autogenerated name
+
+#### Ingress Egress Gw Inside Network Existing Network
+
+An [`existing_network`](#ingress-egress-gw-inside-network-existing-network) block (within [`ingress_egress_gw.inside_network`](#ingress-egress-gw-inside-network)) supports the following:
+
+<a id="ingress-egress-gw-inside-network-existing-network-name"></a>&#x2022; [`name`](#ingress-egress-gw-inside-network-existing-network-name) - Optional String<br>GCP VPC Network Name. Name for your GCP VPC Network
+
+#### Ingress Egress Gw Inside Network New Network
+
+A [`new_network`](#ingress-egress-gw-inside-network-new-network) block (within [`ingress_egress_gw.inside_network`](#ingress-egress-gw-inside-network)) supports the following:
+
+<a id="ingress-egress-gw-inside-network-new-network-name"></a>&#x2022; [`name`](#ingress-egress-gw-inside-network-new-network-name) - Optional String<br>GCP VPC Network Name. Name for your GCP VPC Network
+
+#### Ingress Egress Gw Inside Static Routes
+
+An [`inside_static_routes`](#ingress-egress-gw-inside-static-routes) block (within [`ingress_egress_gw`](#ingress-egress-gw)) supports the following:
+
+<a id="ingress-egress-gw-inside-static-routes-static-route-list"></a>&#x2022; [`static_route_list`](#ingress-egress-gw-inside-static-routes-static-route-list) - Optional Block<br>List of Static Routes. List of Static routes<br>See [Static Route List](#ingress-egress-gw-inside-static-routes-static-route-list) below.
+
+#### Ingress Egress Gw Inside Static Routes Static Route List
+
+A [`static_route_list`](#ingress-egress-gw-inside-static-routes-static-route-list) block (within [`ingress_egress_gw.inside_static_routes`](#ingress-egress-gw-inside-static-routes)) supports the following:
+
+<a id="ingress-egress-gw-inside-static-routes-static-route-list-custom-static-route"></a>&#x2022; [`custom_static_route`](#ingress-egress-gw-inside-static-routes-static-route-list-custom-static-route) - Optional Block<br>Static Route. Defines a static route, configuring a list of prefixes and a next-hop to be used for them<br>See [Custom Static Route](#ingress-egress-gw-inside-static-routes-static-route-list-custom-static-route) below.
+
+<a id="ingress-egress-gw-inside-static-routes-static-route-list-simple-static-route"></a>&#x2022; [`simple_static_route`](#ingress-egress-gw-inside-static-routes-static-route-list-simple-static-route) - Optional String<br>Simple Static Route. Use simple static route for prefix pointing to single interface in the network
+
+#### Ingress Egress Gw Inside Static Routes Static Route List Custom Static Route
+
+A [`custom_static_route`](#ingress-egress-gw-inside-static-routes-static-route-list-custom-static-route) block (within [`ingress_egress_gw.inside_static_routes.static_route_list`](#ingress-egress-gw-inside-static-routes-static-route-list)) supports the following:
+
+<a id="ingress-egress-gw-inside-static-routes-static-route-list-custom-static-route-attrs"></a>&#x2022; [`attrs`](#ingress-egress-gw-inside-static-routes-static-route-list-custom-static-route-attrs) - Optional List  Defaults to `ROUTE_ATTR_NO_OP`<br>Possible values are `ROUTE_ATTR_NO_OP`, `ROUTE_ATTR_ADVERTISE`, `ROUTE_ATTR_INSTALL_HOST`, `ROUTE_ATTR_INSTALL_FORWARDING`, `ROUTE_ATTR_MERGE_ONLY`<br>[Enum: ROUTE_ATTR_NO_OP|ROUTE_ATTR_ADVERTISE|ROUTE_ATTR_INSTALL_HOST|ROUTE_ATTR_INSTALL_FORWARDING|ROUTE_ATTR_MERGE_ONLY] Attributes. List of route attributes associated with the static route
+
+<a id="ingress-egress-gw-inside-static-routes-static-route-list-custom-static-route-labels"></a>&#x2022; [`labels`](#ingress-egress-gw-inside-static-routes-static-route-list-custom-static-route-labels) - Optional Block<br>Static Route Labels. Add Labels for this Static Route, these labels can be used in network policy
+
+<a id="ingress-egress-gw-inside-static-routes-static-route-list-custom-static-route-nexthop"></a>&#x2022; [`nexthop`](#ingress-egress-gw-inside-static-routes-static-route-list-custom-static-route-nexthop) - Optional Block<br>Nexthop. Identifies the next-hop for a route<br>See [Nexthop](#ingress-egress-gw-inside-static-routes-static-route-list-custom-static-route-nexthop) below.
+
+<a id="ingress-egress-gw-inside-static-routes-static-route-list-custom-static-route-subnets"></a>&#x2022; [`subnets`](#ingress-egress-gw-inside-static-routes-static-route-list-custom-static-route-subnets) - Optional Block<br>Subnets. List of route prefixes<br>See [Subnets](#ingress-egress-gw-inside-static-routes-static-route-list-custom-static-route-subnets) below.
+
+#### Ingress Egress Gw Inside Static Routes Static Route List Custom Static Route Nexthop
+
+A [`nexthop`](#ingress-egress-gw-inside-static-routes-static-route-list-custom-static-route-nexthop) block (within [`ingress_egress_gw.inside_static_routes.static_route_list.custom_static_route`](#ingress-egress-gw-inside-static-routes-static-route-list-custom-static-route)) supports the following:
+
+<a id="ingress-egress-gw-inside-static-routes-static-route-list-custom-static-route-nexthop-interface"></a>&#x2022; [`interface`](#ingress-egress-gw-inside-static-routes-static-route-list-custom-static-route-nexthop-interface) - Optional Block<br>Network Interface. Nexthop is network interface when type is 'Network-Interface'<br>See [Interface](#ingress-egress-gw-inside-static-routes-static-route-list-custom-static-route-nexthop-interface) below.
+
+<a id="ingress-egress-gw-inside-static-routes-static-route-list-custom-static-route-nexthop-nexthop-address"></a>&#x2022; [`nexthop_address`](#ingress-egress-gw-inside-static-routes-static-route-list-custom-static-route-nexthop-nexthop-address) - Optional Block<br>IP Address. IP Address used to specify an IPv4 or IPv6 address<br>See [Nexthop Address](#ingress-egress-gw-inside-static-routes-static-route-list-custom-static-route-nexthop-nexthop-address) below.
+
+<a id="ingress-egress-gw-inside-static-routes-static-route-list-custom-static-route-nexthop-type"></a>&#x2022; [`type`](#ingress-egress-gw-inside-static-routes-static-route-list-custom-static-route-nexthop-type) - Optional String  Defaults to `NEXT_HOP_DEFAULT_GATEWAY`<br>Possible values are `NEXT_HOP_DEFAULT_GATEWAY`, `NEXT_HOP_USE_CONFIGURED`, `NEXT_HOP_NETWORK_INTERFACE`<br>[Enum: NEXT_HOP_DEFAULT_GATEWAY|NEXT_HOP_USE_CONFIGURED|NEXT_HOP_NETWORK_INTERFACE] Nexthop Types. Defines types of next-hop Use default gateway on the local interface as gateway for route. Assumes there is only one local interface on the virtual network. Use the specified address as nexthop Use the network interface as nexthop Discard nexthop, used when attr type is Advertise Used in VoltADN private virtual network
+
+#### Ingress Egress Gw Inside Static Routes Static Route List Custom Static Route Nexthop Interface
+
+An [`interface`](#ingress-egress-gw-inside-static-routes-static-route-list-custom-static-route-nexthop-interface) block (within [`ingress_egress_gw.inside_static_routes.static_route_list.custom_static_route.nexthop`](#ingress-egress-gw-inside-static-routes-static-route-list-custom-static-route-nexthop)) supports the following:
+
+<a id="ingress-egress-gw-inside-static-routes-static-route-list-custom-static-route-nexthop-interface-kind"></a>&#x2022; [`kind`](#ingress-egress-gw-inside-static-routes-static-route-list-custom-static-route-nexthop-interface-kind) - Optional String<br>Kind. When a configuration object(e.g. virtual_host) refers to another(e.g route) then kind will hold the referred object's kind (e.g. 'route')
+
+<a id="ingress-egress-gw-inside-static-routes-static-route-list-custom-static-route-nexthop-interface-name"></a>&#x2022; [`name`](#ingress-egress-gw-inside-static-routes-static-route-list-custom-static-route-nexthop-interface-name) - Optional String<br>Name. When a configuration object(e.g. virtual_host) refers to another(e.g route) then name will hold the referred object's(e.g. route's) name
+
+<a id="ingress-egress-gw-inside-static-routes-static-route-list-custom-static-route-nexthop-interface-namespace"></a>&#x2022; [`namespace`](#ingress-egress-gw-inside-static-routes-static-route-list-custom-static-route-nexthop-interface-namespace) - Optional String<br>Namespace. When a configuration object(e.g. virtual_host) refers to another(e.g route) then namespace will hold the referred object's(e.g. route's) namespace
+
+<a id="ingress-egress-gw-inside-static-routes-static-route-list-custom-static-route-nexthop-interface-tenant"></a>&#x2022; [`tenant`](#ingress-egress-gw-inside-static-routes-static-route-list-custom-static-route-nexthop-interface-tenant) - Optional String<br>Tenant. When a configuration object(e.g. virtual_host) refers to another(e.g route) then tenant will hold the referred object's(e.g. route's) tenant
+
+<a id="ingress-egress-gw-inside-static-routes-static-route-list-custom-static-route-nexthop-interface-uid"></a>&#x2022; [`uid`](#ingress-egress-gw-inside-static-routes-static-route-list-custom-static-route-nexthop-interface-uid) - Optional String<br>UID. When a configuration object(e.g. virtual_host) refers to another(e.g route) then uid will hold the referred object's(e.g. route's) uid
+
+#### Ingress Egress Gw Inside Static Routes Static Route List Custom Static Route Nexthop Nexthop Address
+
+A [`nexthop_address`](#ingress-egress-gw-inside-static-routes-static-route-list-custom-static-route-nexthop-nexthop-address) block (within [`ingress_egress_gw.inside_static_routes.static_route_list.custom_static_route.nexthop`](#ingress-egress-gw-inside-static-routes-static-route-list-custom-static-route-nexthop)) supports the following:
+
+<a id="ingress-egress-gw-inside-static-routes-static-route-list-custom-static-route-nexthop-nexthop-address-ipv4"></a>&#x2022; [`ipv4`](#ingress-egress-gw-inside-static-routes-static-route-list-custom-static-route-nexthop-nexthop-address-ipv4) - Optional Block<br>IPv4 Address. IPv4 Address in dot-decimal notation<br>See [IPv4](#ingress-egress-gw-inside-static-routes-static-route-list-custom-static-route-nexthop-nexthop-address-ipv4) below.
+
+<a id="ingress-egress-gw-inside-static-routes-static-route-list-custom-static-route-nexthop-nexthop-address-ipv6"></a>&#x2022; [`ipv6`](#ingress-egress-gw-inside-static-routes-static-route-list-custom-static-route-nexthop-nexthop-address-ipv6) - Optional Block<br>IPv6 Address. IPv6 Address specified as hexadecimal numbers separated by ':'<br>See [IPv6](#ingress-egress-gw-inside-static-routes-static-route-list-custom-static-route-nexthop-nexthop-address-ipv6) below.
+
+#### Ingress Egress Gw Inside Static Routes Static Route List Custom Static Route Nexthop Nexthop Address IPv4
+
+An [`ipv4`](#ingress-egress-gw-inside-static-routes-static-route-list-custom-static-route-nexthop-nexthop-address-ipv4) block (within [`ingress_egress_gw.inside_static_routes.static_route_list.custom_static_route.nexthop.nexthop_address`](#ingress-egress-gw-inside-static-routes-static-route-list-custom-static-route-nexthop-nexthop-address)) supports the following:
+
+<a id="ingress-egress-gw-inside-static-routes-static-route-list-custom-static-route-nexthop-nexthop-address-ipv4-addr"></a>&#x2022; [`addr`](#ingress-egress-gw-inside-static-routes-static-route-list-custom-static-route-nexthop-nexthop-address-ipv4-addr) - Optional String<br>IPv4 Address. IPv4 Address in string form with dot-decimal notation
+
+#### Ingress Egress Gw Inside Static Routes Static Route List Custom Static Route Nexthop Nexthop Address IPv6
+
+An [`ipv6`](#ingress-egress-gw-inside-static-routes-static-route-list-custom-static-route-nexthop-nexthop-address-ipv6) block (within [`ingress_egress_gw.inside_static_routes.static_route_list.custom_static_route.nexthop.nexthop_address`](#ingress-egress-gw-inside-static-routes-static-route-list-custom-static-route-nexthop-nexthop-address)) supports the following:
+
+<a id="ingress-egress-gw-inside-static-routes-static-route-list-custom-static-route-nexthop-nexthop-address-ipv6-addr"></a>&#x2022; [`addr`](#ingress-egress-gw-inside-static-routes-static-route-list-custom-static-route-nexthop-nexthop-address-ipv6-addr) - Optional String<br>IPv6 Address. IPv6 Address in form of string. IPv6 address must be specified as hexadecimal numbers separated by ':' The address can be compacted by suppressing zeros e.g. '2001:db8:0:0:0:0:2:1' becomes '2001:db8::2:1' or '2001:db8:0:0:0:2:0:0' becomes '2001:db8::2::'
+
+#### Ingress Egress Gw Inside Static Routes Static Route List Custom Static Route Subnets
+
+A [`subnets`](#ingress-egress-gw-inside-static-routes-static-route-list-custom-static-route-subnets) block (within [`ingress_egress_gw.inside_static_routes.static_route_list.custom_static_route`](#ingress-egress-gw-inside-static-routes-static-route-list-custom-static-route)) supports the following:
+
+<a id="ingress-egress-gw-inside-static-routes-static-route-list-custom-static-route-subnets-ipv4"></a>&#x2022; [`ipv4`](#ingress-egress-gw-inside-static-routes-static-route-list-custom-static-route-subnets-ipv4) - Optional Block<br>IPv4 Subnet. IPv4 subnets specified as prefix and prefix-length. Prefix length must be <= 32<br>See [IPv4](#ingress-egress-gw-inside-static-routes-static-route-list-custom-static-route-subnets-ipv4) below.
+
+<a id="ingress-egress-gw-inside-static-routes-static-route-list-custom-static-route-subnets-ipv6"></a>&#x2022; [`ipv6`](#ingress-egress-gw-inside-static-routes-static-route-list-custom-static-route-subnets-ipv6) - Optional Block<br>IPv6 Subnet. IPv6 subnets specified as prefix and prefix-length. prefix-legnth must be <= 128<br>See [IPv6](#ingress-egress-gw-inside-static-routes-static-route-list-custom-static-route-subnets-ipv6) below.
+
+#### Ingress Egress Gw Inside Static Routes Static Route List Custom Static Route Subnets IPv4
+
+An [`ipv4`](#ingress-egress-gw-inside-static-routes-static-route-list-custom-static-route-subnets-ipv4) block (within [`ingress_egress_gw.inside_static_routes.static_route_list.custom_static_route.subnets`](#ingress-egress-gw-inside-static-routes-static-route-list-custom-static-route-subnets)) supports the following:
+
+<a id="ingress-egress-gw-inside-static-routes-static-route-list-custom-static-route-subnets-ipv4-plen"></a>&#x2022; [`plen`](#ingress-egress-gw-inside-static-routes-static-route-list-custom-static-route-subnets-ipv4-plen) - Optional Number<br>Prefix Length. Prefix-length of the IPv4 subnet. Must be <= 32
+
+<a id="ingress-egress-gw-inside-static-routes-static-route-list-custom-static-route-subnets-ipv4-prefix"></a>&#x2022; [`prefix`](#ingress-egress-gw-inside-static-routes-static-route-list-custom-static-route-subnets-ipv4-prefix) - Optional String<br>Prefix. Prefix part of the IPv4 subnet in string form with dot-decimal notation
+
+#### Ingress Egress Gw Inside Static Routes Static Route List Custom Static Route Subnets IPv6
+
+An [`ipv6`](#ingress-egress-gw-inside-static-routes-static-route-list-custom-static-route-subnets-ipv6) block (within [`ingress_egress_gw.inside_static_routes.static_route_list.custom_static_route.subnets`](#ingress-egress-gw-inside-static-routes-static-route-list-custom-static-route-subnets)) supports the following:
+
+<a id="ingress-egress-gw-inside-static-routes-static-route-list-custom-static-route-subnets-ipv6-plen"></a>&#x2022; [`plen`](#ingress-egress-gw-inside-static-routes-static-route-list-custom-static-route-subnets-ipv6-plen) - Optional Number<br>Prefix Length. Prefix length of the IPv6 subnet. Must be <= 128
+
+<a id="ingress-egress-gw-inside-static-routes-static-route-list-custom-static-route-subnets-ipv6-prefix"></a>&#x2022; [`prefix`](#ingress-egress-gw-inside-static-routes-static-route-list-custom-static-route-subnets-ipv6-prefix) - Optional String<br>Prefix. Prefix part of the IPv6 subnet given in form of string. IPv6 address must be specified as hexadecimal numbers separated by ':' e.g. '2001:db8:0:0:0:2:0:0' The address can be compacted by suppressing zeros e.g. '2001:db8::2::'
+
+#### Ingress Egress Gw Inside Subnet
+
+An [`inside_subnet`](#ingress-egress-gw-inside-subnet) block (within [`ingress_egress_gw`](#ingress-egress-gw)) supports the following:
+
+<a id="ingress-egress-gw-inside-subnet-existing-subnet"></a>&#x2022; [`existing_subnet`](#ingress-egress-gw-inside-subnet-existing-subnet) - Optional Block<br>GCP existing subnet Type. Name of existing GCP subnet<br>See [Existing Subnet](#ingress-egress-gw-inside-subnet-existing-subnet) below.
+
+<a id="ingress-egress-gw-inside-subnet-new-subnet"></a>&#x2022; [`new_subnet`](#ingress-egress-gw-inside-subnet-new-subnet) - Optional Block<br>GCP subnet parameters Type. Parameters for GCP subnet<br>See [New Subnet](#ingress-egress-gw-inside-subnet-new-subnet) below.
+
+#### Ingress Egress Gw Inside Subnet Existing Subnet
+
+An [`existing_subnet`](#ingress-egress-gw-inside-subnet-existing-subnet) block (within [`ingress_egress_gw.inside_subnet`](#ingress-egress-gw-inside-subnet)) supports the following:
+
+<a id="ingress-egress-gw-inside-subnet-existing-subnet-subnet-name"></a>&#x2022; [`subnet_name`](#ingress-egress-gw-inside-subnet-existing-subnet-subnet-name) - Optional String<br>VPC Subnet Name. Name of your subnet in VPC network
+
+#### Ingress Egress Gw Inside Subnet New Subnet
+
+A [`new_subnet`](#ingress-egress-gw-inside-subnet-new-subnet) block (within [`ingress_egress_gw.inside_subnet`](#ingress-egress-gw-inside-subnet)) supports the following:
+
+<a id="ingress-egress-gw-inside-subnet-new-subnet-primary-ipv4"></a>&#x2022; [`primary_ipv4`](#ingress-egress-gw-inside-subnet-new-subnet-primary-ipv4) - Optional String<br>IPv4 Subnet Prefix. IPv4 prefix for this Subnet. It has to be private address space
+
+<a id="ingress-egress-gw-inside-subnet-new-subnet-subnet-name"></a>&#x2022; [`subnet_name`](#ingress-egress-gw-inside-subnet-new-subnet-subnet-name) - Optional String<br>VPC Subnet Name. Name of new VPC Subnet, will be autogenerated if empty
+
+#### Ingress Egress Gw Outside Network
+
+An [`outside_network`](#ingress-egress-gw-outside-network) block (within [`ingress_egress_gw`](#ingress-egress-gw)) supports the following:
+
+<a id="ingress-egress-gw-outside-network-existing-network"></a>&#x2022; [`existing_network`](#ingress-egress-gw-outside-network-existing-network) - Optional Block<br>GCP existing VPC network Type. Name of existing VPC network<br>See [Existing Network](#ingress-egress-gw-outside-network-existing-network) below.
+
+<a id="ingress-egress-gw-outside-network-new-network"></a>&#x2022; [`new_network`](#ingress-egress-gw-outside-network-new-network) - Optional Block<br>GCP VPC Network Manual Parameters. Parameters to create a new GCP VPC Network<br>See [New Network](#ingress-egress-gw-outside-network-new-network) below.
+
+<a id="ingress-egress-gw-outside-network-new-network-autogenerate"></a>&#x2022; [`new_network_autogenerate`](#ingress-egress-gw-outside-network-new-network-autogenerate) - Optional Block<br>GCP VPC Network Autogenerated Parameters. Create a new GCP VPC Network with autogenerated name
+
+#### Ingress Egress Gw Outside Network Existing Network
+
+An [`existing_network`](#ingress-egress-gw-outside-network-existing-network) block (within [`ingress_egress_gw.outside_network`](#ingress-egress-gw-outside-network)) supports the following:
+
+<a id="ingress-egress-gw-outside-network-existing-network-name"></a>&#x2022; [`name`](#ingress-egress-gw-outside-network-existing-network-name) - Optional String<br>GCP VPC Network Name. Name for your GCP VPC Network
+
+#### Ingress Egress Gw Outside Network New Network
+
+A [`new_network`](#ingress-egress-gw-outside-network-new-network) block (within [`ingress_egress_gw.outside_network`](#ingress-egress-gw-outside-network)) supports the following:
+
+<a id="ingress-egress-gw-outside-network-new-network-name"></a>&#x2022; [`name`](#ingress-egress-gw-outside-network-new-network-name) - Optional String<br>GCP VPC Network Name. Name for your GCP VPC Network
+
+#### Ingress Egress Gw Outside Static Routes
+
+An [`outside_static_routes`](#ingress-egress-gw-outside-static-routes) block (within [`ingress_egress_gw`](#ingress-egress-gw)) supports the following:
+
+<a id="ingress-egress-gw-outside-static-routes-static-route-list"></a>&#x2022; [`static_route_list`](#ingress-egress-gw-outside-static-routes-static-route-list) - Optional Block<br>List of Static Routes. List of Static routes<br>See [Static Route List](#ingress-egress-gw-outside-static-routes-static-route-list) below.
+
+#### Ingress Egress Gw Outside Static Routes Static Route List
+
+A [`static_route_list`](#ingress-egress-gw-outside-static-routes-static-route-list) block (within [`ingress_egress_gw.outside_static_routes`](#ingress-egress-gw-outside-static-routes)) supports the following:
+
+<a id="ingress-egress-gw-outside-static-routes-static-route-list-custom-static-route"></a>&#x2022; [`custom_static_route`](#ingress-egress-gw-outside-static-routes-static-route-list-custom-static-route) - Optional Block<br>Static Route. Defines a static route, configuring a list of prefixes and a next-hop to be used for them<br>See [Custom Static Route](#ingress-egress-gw-outside-static-routes-static-route-list-custom-static-route) below.
+
+<a id="ingress-egress-gw-outside-static-routes-static-route-list-simple-static-route"></a>&#x2022; [`simple_static_route`](#ingress-egress-gw-outside-static-routes-static-route-list-simple-static-route) - Optional String<br>Simple Static Route. Use simple static route for prefix pointing to single interface in the network
+
+#### Ingress Egress Gw Outside Static Routes Static Route List Custom Static Route
+
+A [`custom_static_route`](#ingress-egress-gw-outside-static-routes-static-route-list-custom-static-route) block (within [`ingress_egress_gw.outside_static_routes.static_route_list`](#ingress-egress-gw-outside-static-routes-static-route-list)) supports the following:
+
+<a id="ingress-egress-gw-outside-static-routes-static-route-list-custom-static-route-attrs"></a>&#x2022; [`attrs`](#ingress-egress-gw-outside-static-routes-static-route-list-custom-static-route-attrs) - Optional List  Defaults to `ROUTE_ATTR_NO_OP`<br>Possible values are `ROUTE_ATTR_NO_OP`, `ROUTE_ATTR_ADVERTISE`, `ROUTE_ATTR_INSTALL_HOST`, `ROUTE_ATTR_INSTALL_FORWARDING`, `ROUTE_ATTR_MERGE_ONLY`<br>[Enum: ROUTE_ATTR_NO_OP|ROUTE_ATTR_ADVERTISE|ROUTE_ATTR_INSTALL_HOST|ROUTE_ATTR_INSTALL_FORWARDING|ROUTE_ATTR_MERGE_ONLY] Attributes. List of route attributes associated with the static route
+
+<a id="ingress-egress-gw-outside-static-routes-static-route-list-custom-static-route-labels"></a>&#x2022; [`labels`](#ingress-egress-gw-outside-static-routes-static-route-list-custom-static-route-labels) - Optional Block<br>Static Route Labels. Add Labels for this Static Route, these labels can be used in network policy
+
+<a id="ingress-egress-gw-outside-static-routes-static-route-list-custom-static-route-nexthop"></a>&#x2022; [`nexthop`](#ingress-egress-gw-outside-static-routes-static-route-list-custom-static-route-nexthop) - Optional Block<br>Nexthop. Identifies the next-hop for a route<br>See [Nexthop](#ingress-egress-gw-outside-static-routes-static-route-list-custom-static-route-nexthop) below.
+
+<a id="ingress-egress-gw-outside-static-routes-static-route-list-custom-static-route-subnets"></a>&#x2022; [`subnets`](#ingress-egress-gw-outside-static-routes-static-route-list-custom-static-route-subnets) - Optional Block<br>Subnets. List of route prefixes<br>See [Subnets](#ingress-egress-gw-outside-static-routes-static-route-list-custom-static-route-subnets) below.
+
+#### Ingress Egress Gw Outside Static Routes Static Route List Custom Static Route Nexthop
+
+A [`nexthop`](#ingress-egress-gw-outside-static-routes-static-route-list-custom-static-route-nexthop) block (within [`ingress_egress_gw.outside_static_routes.static_route_list.custom_static_route`](#ingress-egress-gw-outside-static-routes-static-route-list-custom-static-route)) supports the following:
+
+<a id="ingress-egress-gw-outside-static-routes-static-route-list-custom-static-route-nexthop-interface"></a>&#x2022; [`interface`](#ingress-egress-gw-outside-static-routes-static-route-list-custom-static-route-nexthop-interface) - Optional Block<br>Network Interface. Nexthop is network interface when type is 'Network-Interface'<br>See [Interface](#ingress-egress-gw-outside-static-routes-static-route-list-custom-static-route-nexthop-interface) below.
+
+<a id="ingress-egress-gw-outside-static-routes-static-route-list-custom-static-route-nexthop-nexthop-address"></a>&#x2022; [`nexthop_address`](#ingress-egress-gw-outside-static-routes-static-route-list-custom-static-route-nexthop-nexthop-address) - Optional Block<br>IP Address. IP Address used to specify an IPv4 or IPv6 address<br>See [Nexthop Address](#ingress-egress-gw-outside-static-routes-static-route-list-custom-static-route-nexthop-nexthop-address) below.
+
+<a id="ingress-egress-gw-outside-static-routes-static-route-list-custom-static-route-nexthop-type"></a>&#x2022; [`type`](#ingress-egress-gw-outside-static-routes-static-route-list-custom-static-route-nexthop-type) - Optional String  Defaults to `NEXT_HOP_DEFAULT_GATEWAY`<br>Possible values are `NEXT_HOP_DEFAULT_GATEWAY`, `NEXT_HOP_USE_CONFIGURED`, `NEXT_HOP_NETWORK_INTERFACE`<br>[Enum: NEXT_HOP_DEFAULT_GATEWAY|NEXT_HOP_USE_CONFIGURED|NEXT_HOP_NETWORK_INTERFACE] Nexthop Types. Defines types of next-hop Use default gateway on the local interface as gateway for route. Assumes there is only one local interface on the virtual network. Use the specified address as nexthop Use the network interface as nexthop Discard nexthop, used when attr type is Advertise Used in VoltADN private virtual network
+
+#### Ingress Egress Gw Outside Static Routes Static Route List Custom Static Route Nexthop Interface
+
+An [`interface`](#ingress-egress-gw-outside-static-routes-static-route-list-custom-static-route-nexthop-interface) block (within [`ingress_egress_gw.outside_static_routes.static_route_list.custom_static_route.nexthop`](#ingress-egress-gw-outside-static-routes-static-route-list-custom-static-route-nexthop)) supports the following:
+
+<a id="ingress-egress-gw-outside-static-routes-static-route-list-custom-static-route-nexthop-interface-kind"></a>&#x2022; [`kind`](#ingress-egress-gw-outside-static-routes-static-route-list-custom-static-route-nexthop-interface-kind) - Optional String<br>Kind. When a configuration object(e.g. virtual_host) refers to another(e.g route) then kind will hold the referred object's kind (e.g. 'route')
+
+<a id="ingress-egress-gw-outside-static-routes-static-route-list-custom-static-route-nexthop-interface-name"></a>&#x2022; [`name`](#ingress-egress-gw-outside-static-routes-static-route-list-custom-static-route-nexthop-interface-name) - Optional String<br>Name. When a configuration object(e.g. virtual_host) refers to another(e.g route) then name will hold the referred object's(e.g. route's) name
+
+<a id="ingress-egress-gw-outside-static-routes-static-route-list-custom-static-route-nexthop-interface-namespace"></a>&#x2022; [`namespace`](#ingress-egress-gw-outside-static-routes-static-route-list-custom-static-route-nexthop-interface-namespace) - Optional String<br>Namespace. When a configuration object(e.g. virtual_host) refers to another(e.g route) then namespace will hold the referred object's(e.g. route's) namespace
+
+<a id="ingress-egress-gw-outside-static-routes-static-route-list-custom-static-route-nexthop-interface-tenant"></a>&#x2022; [`tenant`](#ingress-egress-gw-outside-static-routes-static-route-list-custom-static-route-nexthop-interface-tenant) - Optional String<br>Tenant. When a configuration object(e.g. virtual_host) refers to another(e.g route) then tenant will hold the referred object's(e.g. route's) tenant
+
+<a id="ingress-egress-gw-outside-static-routes-static-route-list-custom-static-route-nexthop-interface-uid"></a>&#x2022; [`uid`](#ingress-egress-gw-outside-static-routes-static-route-list-custom-static-route-nexthop-interface-uid) - Optional String<br>UID. When a configuration object(e.g. virtual_host) refers to another(e.g route) then uid will hold the referred object's(e.g. route's) uid
+
+#### Ingress Egress Gw Outside Static Routes Static Route List Custom Static Route Nexthop Nexthop Address
+
+A [`nexthop_address`](#ingress-egress-gw-outside-static-routes-static-route-list-custom-static-route-nexthop-nexthop-address) block (within [`ingress_egress_gw.outside_static_routes.static_route_list.custom_static_route.nexthop`](#ingress-egress-gw-outside-static-routes-static-route-list-custom-static-route-nexthop)) supports the following:
+
+<a id="ingress-egress-gw-outside-static-routes-static-route-list-custom-static-route-nexthop-nexthop-address-ipv4"></a>&#x2022; [`ipv4`](#ingress-egress-gw-outside-static-routes-static-route-list-custom-static-route-nexthop-nexthop-address-ipv4) - Optional Block<br>IPv4 Address. IPv4 Address in dot-decimal notation<br>See [IPv4](#ingress-egress-gw-outside-static-routes-static-route-list-custom-static-route-nexthop-nexthop-address-ipv4) below.
+
+<a id="ingress-egress-gw-outside-static-routes-static-route-list-custom-static-route-nexthop-nexthop-address-ipv6"></a>&#x2022; [`ipv6`](#ingress-egress-gw-outside-static-routes-static-route-list-custom-static-route-nexthop-nexthop-address-ipv6) - Optional Block<br>IPv6 Address. IPv6 Address specified as hexadecimal numbers separated by ':'<br>See [IPv6](#ingress-egress-gw-outside-static-routes-static-route-list-custom-static-route-nexthop-nexthop-address-ipv6) below.
+
+#### Ingress Egress Gw Outside Static Routes Static Route List Custom Static Route Nexthop Nexthop Address IPv4
+
+An [`ipv4`](#ingress-egress-gw-outside-static-routes-static-route-list-custom-static-route-nexthop-nexthop-address-ipv4) block (within [`ingress_egress_gw.outside_static_routes.static_route_list.custom_static_route.nexthop.nexthop_address`](#ingress-egress-gw-outside-static-routes-static-route-list-custom-static-route-nexthop-nexthop-address)) supports the following:
+
+<a id="ingress-egress-gw-outside-static-routes-static-route-list-custom-static-route-nexthop-nexthop-address-ipv4-addr"></a>&#x2022; [`addr`](#ingress-egress-gw-outside-static-routes-static-route-list-custom-static-route-nexthop-nexthop-address-ipv4-addr) - Optional String<br>IPv4 Address. IPv4 Address in string form with dot-decimal notation
+
+#### Ingress Egress Gw Outside Static Routes Static Route List Custom Static Route Nexthop Nexthop Address IPv6
+
+An [`ipv6`](#ingress-egress-gw-outside-static-routes-static-route-list-custom-static-route-nexthop-nexthop-address-ipv6) block (within [`ingress_egress_gw.outside_static_routes.static_route_list.custom_static_route.nexthop.nexthop_address`](#ingress-egress-gw-outside-static-routes-static-route-list-custom-static-route-nexthop-nexthop-address)) supports the following:
+
+<a id="ingress-egress-gw-outside-static-routes-static-route-list-custom-static-route-nexthop-nexthop-address-ipv6-addr"></a>&#x2022; [`addr`](#ingress-egress-gw-outside-static-routes-static-route-list-custom-static-route-nexthop-nexthop-address-ipv6-addr) - Optional String<br>IPv6 Address. IPv6 Address in form of string. IPv6 address must be specified as hexadecimal numbers separated by ':' The address can be compacted by suppressing zeros e.g. '2001:db8:0:0:0:0:2:1' becomes '2001:db8::2:1' or '2001:db8:0:0:0:2:0:0' becomes '2001:db8::2::'
+
+#### Ingress Egress Gw Outside Static Routes Static Route List Custom Static Route Subnets
+
+A [`subnets`](#ingress-egress-gw-outside-static-routes-static-route-list-custom-static-route-subnets) block (within [`ingress_egress_gw.outside_static_routes.static_route_list.custom_static_route`](#ingress-egress-gw-outside-static-routes-static-route-list-custom-static-route)) supports the following:
+
+<a id="ingress-egress-gw-outside-static-routes-static-route-list-custom-static-route-subnets-ipv4"></a>&#x2022; [`ipv4`](#ingress-egress-gw-outside-static-routes-static-route-list-custom-static-route-subnets-ipv4) - Optional Block<br>IPv4 Subnet. IPv4 subnets specified as prefix and prefix-length. Prefix length must be <= 32<br>See [IPv4](#ingress-egress-gw-outside-static-routes-static-route-list-custom-static-route-subnets-ipv4) below.
+
+<a id="ingress-egress-gw-outside-static-routes-static-route-list-custom-static-route-subnets-ipv6"></a>&#x2022; [`ipv6`](#ingress-egress-gw-outside-static-routes-static-route-list-custom-static-route-subnets-ipv6) - Optional Block<br>IPv6 Subnet. IPv6 subnets specified as prefix and prefix-length. prefix-legnth must be <= 128<br>See [IPv6](#ingress-egress-gw-outside-static-routes-static-route-list-custom-static-route-subnets-ipv6) below.
+
+#### Ingress Egress Gw Outside Static Routes Static Route List Custom Static Route Subnets IPv4
+
+An [`ipv4`](#ingress-egress-gw-outside-static-routes-static-route-list-custom-static-route-subnets-ipv4) block (within [`ingress_egress_gw.outside_static_routes.static_route_list.custom_static_route.subnets`](#ingress-egress-gw-outside-static-routes-static-route-list-custom-static-route-subnets)) supports the following:
+
+<a id="ingress-egress-gw-outside-static-routes-static-route-list-custom-static-route-subnets-ipv4-plen"></a>&#x2022; [`plen`](#ingress-egress-gw-outside-static-routes-static-route-list-custom-static-route-subnets-ipv4-plen) - Optional Number<br>Prefix Length. Prefix-length of the IPv4 subnet. Must be <= 32
+
+<a id="ingress-egress-gw-outside-static-routes-static-route-list-custom-static-route-subnets-ipv4-prefix"></a>&#x2022; [`prefix`](#ingress-egress-gw-outside-static-routes-static-route-list-custom-static-route-subnets-ipv4-prefix) - Optional String<br>Prefix. Prefix part of the IPv4 subnet in string form with dot-decimal notation
+
+#### Ingress Egress Gw Outside Static Routes Static Route List Custom Static Route Subnets IPv6
+
+An [`ipv6`](#ingress-egress-gw-outside-static-routes-static-route-list-custom-static-route-subnets-ipv6) block (within [`ingress_egress_gw.outside_static_routes.static_route_list.custom_static_route.subnets`](#ingress-egress-gw-outside-static-routes-static-route-list-custom-static-route-subnets)) supports the following:
+
+<a id="ingress-egress-gw-outside-static-routes-static-route-list-custom-static-route-subnets-ipv6-plen"></a>&#x2022; [`plen`](#ingress-egress-gw-outside-static-routes-static-route-list-custom-static-route-subnets-ipv6-plen) - Optional Number<br>Prefix Length. Prefix length of the IPv6 subnet. Must be <= 128
+
+<a id="ingress-egress-gw-outside-static-routes-static-route-list-custom-static-route-subnets-ipv6-prefix"></a>&#x2022; [`prefix`](#ingress-egress-gw-outside-static-routes-static-route-list-custom-static-route-subnets-ipv6-prefix) - Optional String<br>Prefix. Prefix part of the IPv6 subnet given in form of string. IPv6 address must be specified as hexadecimal numbers separated by ':' e.g. '2001:db8:0:0:0:2:0:0' The address can be compacted by suppressing zeros e.g. '2001:db8::2::'
+
+#### Ingress Egress Gw Outside Subnet
+
+An [`outside_subnet`](#ingress-egress-gw-outside-subnet) block (within [`ingress_egress_gw`](#ingress-egress-gw)) supports the following:
+
+<a id="ingress-egress-gw-outside-subnet-existing-subnet"></a>&#x2022; [`existing_subnet`](#ingress-egress-gw-outside-subnet-existing-subnet) - Optional Block<br>GCP existing subnet Type. Name of existing GCP subnet<br>See [Existing Subnet](#ingress-egress-gw-outside-subnet-existing-subnet) below.
+
+<a id="ingress-egress-gw-outside-subnet-new-subnet"></a>&#x2022; [`new_subnet`](#ingress-egress-gw-outside-subnet-new-subnet) - Optional Block<br>GCP subnet parameters Type. Parameters for GCP subnet<br>See [New Subnet](#ingress-egress-gw-outside-subnet-new-subnet) below.
+
+#### Ingress Egress Gw Outside Subnet Existing Subnet
+
+An [`existing_subnet`](#ingress-egress-gw-outside-subnet-existing-subnet) block (within [`ingress_egress_gw.outside_subnet`](#ingress-egress-gw-outside-subnet)) supports the following:
+
+<a id="ingress-egress-gw-outside-subnet-existing-subnet-subnet-name"></a>&#x2022; [`subnet_name`](#ingress-egress-gw-outside-subnet-existing-subnet-subnet-name) - Optional String<br>VPC Subnet Name. Name of your subnet in VPC network
+
+#### Ingress Egress Gw Outside Subnet New Subnet
+
+A [`new_subnet`](#ingress-egress-gw-outside-subnet-new-subnet) block (within [`ingress_egress_gw.outside_subnet`](#ingress-egress-gw-outside-subnet)) supports the following:
+
+<a id="ingress-egress-gw-outside-subnet-new-subnet-primary-ipv4"></a>&#x2022; [`primary_ipv4`](#ingress-egress-gw-outside-subnet-new-subnet-primary-ipv4) - Optional String<br>IPv4 Subnet Prefix. IPv4 prefix for this Subnet. It has to be private address space
+
+<a id="ingress-egress-gw-outside-subnet-new-subnet-subnet-name"></a>&#x2022; [`subnet_name`](#ingress-egress-gw-outside-subnet-new-subnet-subnet-name) - Optional String<br>VPC Subnet Name. Name of new VPC Subnet, will be autogenerated if empty
+
+#### Ingress Egress Gw Performance Enhancement Mode
+
+A [`performance_enhancement_mode`](#ingress-egress-gw-performance-enhancement-mode) block (within [`ingress_egress_gw`](#ingress-egress-gw)) supports the following:
+
+<a id="ingress-egress-gw-performance-enhancement-mode-perf-mode-l3-enhanced"></a>&#x2022; [`perf_mode_l3_enhanced`](#ingress-egress-gw-performance-enhancement-mode-perf-mode-l3-enhanced) - Optional Block<br>L3 Mode Enhanced Performance.L3 enhanced performance mode options<br>See [Perf Mode L3 Enhanced](#ingress-egress-gw-performance-enhancement-mode-perf-mode-l3-enhanced) below.
+
+<a id="ingress-egress-gw-performance-enhancement-mode-perf-mode-l7-enhanced"></a>&#x2022; [`perf_mode_l7_enhanced`](#ingress-egress-gw-performance-enhancement-mode-perf-mode-l7-enhanced) - Optional Block<br>Enable this option
+
+#### Ingress Egress Gw Performance Enhancement Mode Perf Mode L3 Enhanced
+
+A [`perf_mode_l3_enhanced`](#ingress-egress-gw-performance-enhancement-mode-perf-mode-l3-enhanced) block (within [`ingress_egress_gw.performance_enhancement_mode`](#ingress-egress-gw-performance-enhancement-mode)) supports the following:
+
+<a id="ingress-egress-gw-performance-enhancement-mode-perf-mode-l3-enhanced-jumbo"></a>&#x2022; [`jumbo`](#ingress-egress-gw-performance-enhancement-mode-perf-mode-l3-enhanced-jumbo) - Optional Block<br>Enable this option
+
+<a id="ingress-egress-gw-performance-enhancement-mode-perf-mode-l3-enhanced-no-jumbo"></a>&#x2022; [`no_jumbo`](#ingress-egress-gw-performance-enhancement-mode-perf-mode-l3-enhanced-no-jumbo) - Optional Block<br>Enable this option
+
+#### Ingress Gw
+
+An [`ingress_gw`](#ingress-gw) block supports the following:
+
+<a id="ingress-gw-gcp-certified-hw"></a>&#x2022; [`gcp_certified_hw`](#ingress-gw-gcp-certified-hw) - Optional String<br>GCP Certified Hardware. Name for GCP certified hardware
+
+<a id="ingress-gw-gcp-zone-names"></a>&#x2022; [`gcp_zone_names`](#ingress-gw-gcp-zone-names) - Optional List<br>GCP zone names.List of zones when instances will be created, needs to match with region selected
+
+<a id="ingress-gw-local-network"></a>&#x2022; [`local_network`](#ingress-gw-local-network) - Optional Block<br>GCP VPC network choice. This defines choice about GCP VPC network for a view<br>See [Local Network](#ingress-gw-local-network) below.
+
+<a id="ingress-gw-local-subnet"></a>&#x2022; [`local_subnet`](#ingress-gw-local-subnet) - Optional Block<br>GCP VPC network choice. This defines choice about GCP VPC network for a view<br>See [Local Subnet](#ingress-gw-local-subnet) below.
+
+<a id="ingress-gw-node-number"></a>&#x2022; [`node_number`](#ingress-gw-node-number) - Optional Number<br>Number of main nodes. Number of main nodes to create, either 1 or 3
+
+<a id="ingress-gw-performance-enhancement-mode"></a>&#x2022; [`performance_enhancement_mode`](#ingress-gw-performance-enhancement-mode) - Optional Block<br>Performance Enhancement Mode.Optimize the site for L3 or L7 traffic processing. L7 optimized is the default<br>See [Performance Enhancement Mode](#ingress-gw-performance-enhancement-mode) below.
+
+#### Ingress Gw Local Network
+
+A [`local_network`](#ingress-gw-local-network) block (within [`ingress_gw`](#ingress-gw)) supports the following:
+
+<a id="ingress-gw-local-network-existing-network"></a>&#x2022; [`existing_network`](#ingress-gw-local-network-existing-network) - Optional Block<br>GCP existing VPC network Type. Name of existing VPC network<br>See [Existing Network](#ingress-gw-local-network-existing-network) below.
+
+<a id="ingress-gw-local-network-new-network"></a>&#x2022; [`new_network`](#ingress-gw-local-network-new-network) - Optional Block<br>GCP VPC Network Manual Parameters. Parameters to create a new GCP VPC Network<br>See [New Network](#ingress-gw-local-network-new-network) below.
+
+<a id="ingress-gw-local-network-new-network-autogenerate"></a>&#x2022; [`new_network_autogenerate`](#ingress-gw-local-network-new-network-autogenerate) - Optional Block<br>GCP VPC Network Autogenerated Parameters. Create a new GCP VPC Network with autogenerated name
+
+#### Ingress Gw Local Network Existing Network
+
+An [`existing_network`](#ingress-gw-local-network-existing-network) block (within [`ingress_gw.local_network`](#ingress-gw-local-network)) supports the following:
+
+<a id="ingress-gw-local-network-existing-network-name"></a>&#x2022; [`name`](#ingress-gw-local-network-existing-network-name) - Optional String<br>GCP VPC Network Name. Name for your GCP VPC Network
+
+#### Ingress Gw Local Network New Network
+
+A [`new_network`](#ingress-gw-local-network-new-network) block (within [`ingress_gw.local_network`](#ingress-gw-local-network)) supports the following:
+
+<a id="ingress-gw-local-network-new-network-name"></a>&#x2022; [`name`](#ingress-gw-local-network-new-network-name) - Optional String<br>GCP VPC Network Name. Name for your GCP VPC Network
+
+#### Ingress Gw Local Subnet
+
+A [`local_subnet`](#ingress-gw-local-subnet) block (within [`ingress_gw`](#ingress-gw)) supports the following:
+
+<a id="ingress-gw-local-subnet-existing-subnet"></a>&#x2022; [`existing_subnet`](#ingress-gw-local-subnet-existing-subnet) - Optional Block<br>GCP existing subnet Type. Name of existing GCP subnet<br>See [Existing Subnet](#ingress-gw-local-subnet-existing-subnet) below.
+
+<a id="ingress-gw-local-subnet-new-subnet"></a>&#x2022; [`new_subnet`](#ingress-gw-local-subnet-new-subnet) - Optional Block<br>GCP subnet parameters Type. Parameters for GCP subnet<br>See [New Subnet](#ingress-gw-local-subnet-new-subnet) below.
+
+#### Ingress Gw Local Subnet Existing Subnet
+
+An [`existing_subnet`](#ingress-gw-local-subnet-existing-subnet) block (within [`ingress_gw.local_subnet`](#ingress-gw-local-subnet)) supports the following:
+
+<a id="ingress-gw-local-subnet-existing-subnet-subnet-name"></a>&#x2022; [`subnet_name`](#ingress-gw-local-subnet-existing-subnet-subnet-name) - Optional String<br>VPC Subnet Name. Name of your subnet in VPC network
+
+#### Ingress Gw Local Subnet New Subnet
+
+A [`new_subnet`](#ingress-gw-local-subnet-new-subnet) block (within [`ingress_gw.local_subnet`](#ingress-gw-local-subnet)) supports the following:
+
+<a id="ingress-gw-local-subnet-new-subnet-primary-ipv4"></a>&#x2022; [`primary_ipv4`](#ingress-gw-local-subnet-new-subnet-primary-ipv4) - Optional String<br>IPv4 Subnet Prefix. IPv4 prefix for this Subnet. It has to be private address space
+
+<a id="ingress-gw-local-subnet-new-subnet-subnet-name"></a>&#x2022; [`subnet_name`](#ingress-gw-local-subnet-new-subnet-subnet-name) - Optional String<br>VPC Subnet Name. Name of new VPC Subnet, will be autogenerated if empty
+
+#### Ingress Gw Performance Enhancement Mode
+
+A [`performance_enhancement_mode`](#ingress-gw-performance-enhancement-mode) block (within [`ingress_gw`](#ingress-gw)) supports the following:
+
+<a id="ingress-gw-performance-enhancement-mode-perf-mode-l3-enhanced"></a>&#x2022; [`perf_mode_l3_enhanced`](#ingress-gw-performance-enhancement-mode-perf-mode-l3-enhanced) - Optional Block<br>L3 Mode Enhanced Performance.L3 enhanced performance mode options<br>See [Perf Mode L3 Enhanced](#ingress-gw-performance-enhancement-mode-perf-mode-l3-enhanced) below.
+
+<a id="ingress-gw-performance-enhancement-mode-perf-mode-l7-enhanced"></a>&#x2022; [`perf_mode_l7_enhanced`](#ingress-gw-performance-enhancement-mode-perf-mode-l7-enhanced) - Optional Block<br>Enable this option
+
+#### Ingress Gw Performance Enhancement Mode Perf Mode L3 Enhanced
+
+A [`perf_mode_l3_enhanced`](#ingress-gw-performance-enhancement-mode-perf-mode-l3-enhanced) block (within [`ingress_gw.performance_enhancement_mode`](#ingress-gw-performance-enhancement-mode)) supports the following:
+
+<a id="ingress-gw-performance-enhancement-mode-perf-mode-l3-enhanced-jumbo"></a>&#x2022; [`jumbo`](#ingress-gw-performance-enhancement-mode-perf-mode-l3-enhanced-jumbo) - Optional Block<br>Enable this option
+
+<a id="ingress-gw-performance-enhancement-mode-perf-mode-l3-enhanced-no-jumbo"></a>&#x2022; [`no_jumbo`](#ingress-gw-performance-enhancement-mode-perf-mode-l3-enhanced-no-jumbo) - Optional Block<br>Enable this option
+
+#### Kubernetes Upgrade Drain
+
+A [`kubernetes_upgrade_drain`](#kubernetes-upgrade-drain) block supports the following:
+
+<a id="kubernetes-upgrade-drain-disable-upgrade-drain"></a>&#x2022; [`disable_upgrade_drain`](#kubernetes-upgrade-drain-disable-upgrade-drain) - Optional Block<br>Enable this option
+
+<a id="kubernetes-upgrade-drain-enable-upgrade-drain"></a>&#x2022; [`enable_upgrade_drain`](#kubernetes-upgrade-drain-enable-upgrade-drain) - Optional Block<br>Enable Node by Node Upgrade. Specify batch upgrade settings for worker nodes within a site<br>See [Enable Upgrade Drain](#kubernetes-upgrade-drain-enable-upgrade-drain) below.
+
+#### Kubernetes Upgrade Drain Enable Upgrade Drain
+
+An [`enable_upgrade_drain`](#kubernetes-upgrade-drain-enable-upgrade-drain) block (within [`kubernetes_upgrade_drain`](#kubernetes-upgrade-drain)) supports the following:
+
+<a id="kubernetes-upgrade-drain-enable-upgrade-drain-disable-vega-upgrade-mode"></a>&#x2022; [`disable_vega_upgrade_mode`](#kubernetes-upgrade-drain-enable-upgrade-drain-disable-vega-upgrade-mode) - Optional Block<br>Enable this option
+
+<a id="kubernetes-upgrade-drain-enable-upgrade-drain-drain-max-unavailable-node-count"></a>&#x2022; [`drain_max_unavailable_node_count`](#kubernetes-upgrade-drain-enable-upgrade-drain-drain-max-unavailable-node-count) - Optional Number<br>Node Batch Size Count
+
+<a id="kubernetes-upgrade-drain-enable-upgrade-drain-drain-node-timeout"></a>&#x2022; [`drain_node_timeout`](#kubernetes-upgrade-drain-enable-upgrade-drain-drain-node-timeout) - Optional Number<br>Upgrade Wait Time. Seconds to wait before initiating upgrade on the next set of nodes. Setting it to 0 will wait indefinitely for all services on nodes to be upgraded gracefully before proceeding to the next set of nodes. (Warning: It may block upgrade if services on a node cannot be gracefully upgraded. It is recommended to use the default value)
+
+<a id="kubernetes-upgrade-drain-enable-upgrade-drain-enable-vega-upgrade-mode"></a>&#x2022; [`enable_vega_upgrade_mode`](#kubernetes-upgrade-drain-enable-upgrade-drain-enable-vega-upgrade-mode) - Optional Block<br>Enable this option
+
+#### Log Receiver
+
+A [`log_receiver`](#log-receiver) block supports the following:
+
+<a id="log-receiver-name"></a>&#x2022; [`name`](#log-receiver-name) - Optional String<br>Name. When a configuration object(e.g. virtual_host) refers to another(e.g route) then name will hold the referred object's(e.g. route's) name
+
+<a id="log-receiver-namespace"></a>&#x2022; [`namespace`](#log-receiver-namespace) - Optional String<br>Namespace. When a configuration object(e.g. virtual_host) refers to another(e.g route) then namespace will hold the referred object's(e.g. route's) namespace
+
+<a id="log-receiver-tenant"></a>&#x2022; [`tenant`](#log-receiver-tenant) - Optional String<br>Tenant. When a configuration object(e.g. virtual_host) refers to another(e.g route) then tenant will hold the referred object's(e.g. route's) tenant
+
+#### Offline Survivability Mode
+
+An [`offline_survivability_mode`](#offline-survivability-mode) block supports the following:
+
+<a id="offline-survivability-mode-enable-offline-survivability-mode"></a>&#x2022; [`enable_offline_survivability_mode`](#offline-survivability-mode-enable-offline-survivability-mode) - Optional Block<br>Enable this option
+
+<a id="offline-survivability-mode-no-offline-survivability-mode"></a>&#x2022; [`no_offline_survivability_mode`](#offline-survivability-mode-no-offline-survivability-mode) - Optional Block<br>Enable this option
+
+#### OS
+
+An [`os`](#os) block supports the following:
+
+<a id="os-default-os-version"></a>&#x2022; [`default_os_version`](#os-default-os-version) - Optional Block<br>Enable this option
+
+<a id="os-operating-system-version"></a>&#x2022; [`operating_system_version`](#os-operating-system-version) - Optional String<br>Operating System Version. Specify a OS version to be used e.g. 9.2024.6
+
+#### Private Connectivity
+
+A [`private_connectivity`](#private-connectivity) block supports the following:
+
+<a id="private-connectivity-cloud-link"></a>&#x2022; [`cloud_link`](#private-connectivity-cloud-link) - Optional Block<br>Object reference. This type establishes a direct reference from one object(the referrer) to another(the referred). Such a reference is in form of tenant/namespace/name<br>See [Cloud Link](#private-connectivity-cloud-link) below.
+
+<a id="private-connectivity-inside"></a>&#x2022; [`inside`](#private-connectivity-inside) - Optional Block<br>Enable this option
+
+<a id="private-connectivity-outside"></a>&#x2022; [`outside`](#private-connectivity-outside) - Optional Block<br>Enable this option
+
+#### Private Connectivity Cloud Link
+
+A [`cloud_link`](#private-connectivity-cloud-link) block (within [`private_connectivity`](#private-connectivity)) supports the following:
+
+<a id="private-connectivity-cloud-link-name"></a>&#x2022; [`name`](#private-connectivity-cloud-link-name) - Optional String<br>Name. When a configuration object(e.g. virtual_host) refers to another(e.g route) then name will hold the referred object's(e.g. route's) name
+
+<a id="private-connectivity-cloud-link-namespace"></a>&#x2022; [`namespace`](#private-connectivity-cloud-link-namespace) - Optional String<br>Namespace. When a configuration object(e.g. virtual_host) refers to another(e.g route) then namespace will hold the referred object's(e.g. route's) namespace
+
+<a id="private-connectivity-cloud-link-tenant"></a>&#x2022; [`tenant`](#private-connectivity-cloud-link-tenant) - Optional String<br>Tenant. When a configuration object(e.g. virtual_host) refers to another(e.g route) then tenant will hold the referred object's(e.g. route's) tenant
+
+#### Sw
+
+A [`sw`](#sw) block supports the following:
+
+<a id="sw-default-sw-version"></a>&#x2022; [`default_sw_version`](#sw-default-sw-version) - Optional Block<br>Enable this option
+
+<a id="sw-volterra-software-version"></a>&#x2022; [`volterra_software_version`](#sw-volterra-software-version) - Optional String<br>F5XC Software Version. Specify a F5XC Software Version to be used e.g. crt-20210329-1002
+
+#### Timeouts
+
+A [`timeouts`](#timeouts) block supports the following:
+
+<a id="timeouts-create"></a>&#x2022; [`create`](#timeouts-create) - Optional String (Defaults to `30 minutes`)<br>Used when creating the resource
+
+<a id="timeouts-delete"></a>&#x2022; [`delete`](#timeouts-delete) - Optional String (Defaults to `30 minutes`)<br>Used when deleting the resource
+
+<a id="timeouts-read"></a>&#x2022; [`read`](#timeouts-read) - Optional String (Defaults to `5 minutes`)<br>Used when retrieving the resource
+
+<a id="timeouts-update"></a>&#x2022; [`update`](#timeouts-update) - Optional String (Defaults to `30 minutes`)<br>Used when updating the resource
+
+#### Voltstack Cluster
+
+A [`voltstack_cluster`](#voltstack-cluster) block supports the following:
+
+<a id="voltstack-cluster-active-enhanced-firewall-policies"></a>&#x2022; [`active_enhanced_firewall_policies`](#voltstack-cluster-active-enhanced-firewall-policies) - Optional Block<br>Active Enhanced Network Policies Type. List of Enhanced Firewall Policies These policies use session-based rules and provide all options available under firewall policies with an additional option for service insertion<br>See [Active Enhanced Firewall Policies](#voltstack-cluster-active-enhanced-firewall-policies) below.
+
+<a id="voltstack-cluster-active-forward-proxy-policies"></a>&#x2022; [`active_forward_proxy_policies`](#voltstack-cluster-active-forward-proxy-policies) - Optional Block<br>Active Forward Proxy Policies Type. Ordered List of Forward Proxy Policies active<br>See [Active Forward Proxy Policies](#voltstack-cluster-active-forward-proxy-policies) below.
+
+<a id="voltstack-cluster-active-network-policies"></a>&#x2022; [`active_network_policies`](#voltstack-cluster-active-network-policies) - Optional Block<br>Active Firewall Policies Type. List of firewall policy views<br>See [Active Network Policies](#voltstack-cluster-active-network-policies) below.
+
+<a id="voltstack-cluster-dc-cluster-group"></a>&#x2022; [`dc_cluster_group`](#voltstack-cluster-dc-cluster-group) - Optional Block<br>Object reference. This type establishes a direct reference from one object(the referrer) to another(the referred). Such a reference is in form of tenant/namespace/name<br>See [Dc Cluster Group](#voltstack-cluster-dc-cluster-group) below.
+
+<a id="voltstack-cluster-default-storage"></a>&#x2022; [`default_storage`](#voltstack-cluster-default-storage) - Optional Block<br>Enable this option
+
+<a id="voltstack-cluster-forward-proxy-allow-all"></a>&#x2022; [`forward_proxy_allow_all`](#voltstack-cluster-forward-proxy-allow-all) - Optional Block<br>Enable this option
+
+<a id="voltstack-cluster-gcp-certified-hw"></a>&#x2022; [`gcp_certified_hw`](#voltstack-cluster-gcp-certified-hw) - Optional String<br>GCP Certified Hardware. Name for GCP certified hardware
+
+<a id="voltstack-cluster-gcp-zone-names"></a>&#x2022; [`gcp_zone_names`](#voltstack-cluster-gcp-zone-names) - Optional List<br>GCP zone names.List of zones when instances will be created, needs to match with region selected
+
+<a id="voltstack-cluster-global-network-list"></a>&#x2022; [`global_network_list`](#voltstack-cluster-global-network-list) - Optional Block<br>Global Network Connection List. List of global network connections<br>See [Global Network List](#voltstack-cluster-global-network-list) below.
+
+<a id="voltstack-cluster-k8s-cluster"></a>&#x2022; [`k8s_cluster`](#voltstack-cluster-k8s-cluster) - Optional Block<br>Object reference. This type establishes a direct reference from one object(the referrer) to another(the referred). Such a reference is in form of tenant/namespace/name<br>See [K8S Cluster](#voltstack-cluster-k8s-cluster) below.
+
+<a id="voltstack-cluster-no-dc-cluster-group"></a>&#x2022; [`no_dc_cluster_group`](#voltstack-cluster-no-dc-cluster-group) - Optional Block<br>Enable this option
+
+<a id="voltstack-cluster-no-forward-proxy"></a>&#x2022; [`no_forward_proxy`](#voltstack-cluster-no-forward-proxy) - Optional Block<br>Enable this option
+
+<a id="voltstack-cluster-no-global-network"></a>&#x2022; [`no_global_network`](#voltstack-cluster-no-global-network) - Optional Block<br>Enable this option
+
+<a id="voltstack-cluster-no-k8s-cluster"></a>&#x2022; [`no_k8s_cluster`](#voltstack-cluster-no-k8s-cluster) - Optional Block<br>Enable this option
+
+<a id="voltstack-cluster-no-network-policy"></a>&#x2022; [`no_network_policy`](#voltstack-cluster-no-network-policy) - Optional Block<br>Enable this option
+
+<a id="voltstack-cluster-no-outside-static-routes"></a>&#x2022; [`no_outside_static_routes`](#voltstack-cluster-no-outside-static-routes) - Optional Block<br>Enable this option
+
+<a id="voltstack-cluster-node-number"></a>&#x2022; [`node_number`](#voltstack-cluster-node-number) - Optional Number<br>Number of main Nodes. Number of main nodes to create, either 1 or 3
+
+<a id="voltstack-cluster-outside-static-routes"></a>&#x2022; [`outside_static_routes`](#voltstack-cluster-outside-static-routes) - Optional Block<br>Static Route List Type. List of static routes<br>See [Outside Static Routes](#voltstack-cluster-outside-static-routes) below.
+
+<a id="voltstack-cluster-site-local-network"></a>&#x2022; [`site_local_network`](#voltstack-cluster-site-local-network) - Optional Block<br>GCP VPC network choice. This defines choice about GCP VPC network for a view<br>See [Site Local Network](#voltstack-cluster-site-local-network) below.
+
+<a id="voltstack-cluster-site-local-subnet"></a>&#x2022; [`site_local_subnet`](#voltstack-cluster-site-local-subnet) - Optional Block<br>GCP VPC network choice. This defines choice about GCP VPC network for a view<br>See [Site Local Subnet](#voltstack-cluster-site-local-subnet) below.
+
+<a id="voltstack-cluster-sm-connection-public-ip"></a>&#x2022; [`sm_connection_public_ip`](#voltstack-cluster-sm-connection-public-ip) - Optional Block<br>Enable this option
+
+<a id="voltstack-cluster-sm-connection-pvt-ip"></a>&#x2022; [`sm_connection_pvt_ip`](#voltstack-cluster-sm-connection-pvt-ip) - Optional Block<br>Enable this option
+
+<a id="voltstack-cluster-storage-class-list"></a>&#x2022; [`storage_class_list`](#voltstack-cluster-storage-class-list) - Optional Block<br>Custom Storage Class List. Add additional custom storage classes in kubernetes for this site<br>See [Storage Class List](#voltstack-cluster-storage-class-list) below.
+
+#### Voltstack Cluster Active Enhanced Firewall Policies
+
+An [`active_enhanced_firewall_policies`](#voltstack-cluster-active-enhanced-firewall-policies) block (within [`voltstack_cluster`](#voltstack-cluster)) supports the following:
+
+<a id="voltstack-cluster-active-enhanced-firewall-policies-enhanced-firewall-policies"></a>&#x2022; [`enhanced_firewall_policies`](#voltstack-cluster-active-enhanced-firewall-policies-enhanced-firewall-policies) - Optional Block<br>Enhanced Firewall Policy. Ordered List of Enhanced Firewall Policies active<br>See [Enhanced Firewall Policies](#voltstack-cluster-active-enhanced-firewall-policies-enhanced-firewall-policies) below.
+
+#### Voltstack Cluster Active Enhanced Firewall Policies Enhanced Firewall Policies
+
+An [`enhanced_firewall_policies`](#voltstack-cluster-active-enhanced-firewall-policies-enhanced-firewall-policies) block (within [`voltstack_cluster.active_enhanced_firewall_policies`](#voltstack-cluster-active-enhanced-firewall-policies)) supports the following:
+
+<a id="voltstack-cluster-active-enhanced-firewall-policies-enhanced-firewall-policies-name"></a>&#x2022; [`name`](#voltstack-cluster-active-enhanced-firewall-policies-enhanced-firewall-policies-name) - Optional String<br>Name. When a configuration object(e.g. virtual_host) refers to another(e.g route) then name will hold the referred object's(e.g. route's) name
+
+<a id="voltstack-cluster-active-enhanced-firewall-policies-enhanced-firewall-policies-namespace"></a>&#x2022; [`namespace`](#voltstack-cluster-active-enhanced-firewall-policies-enhanced-firewall-policies-namespace) - Optional String<br>Namespace. When a configuration object(e.g. virtual_host) refers to another(e.g route) then namespace will hold the referred object's(e.g. route's) namespace
+
+<a id="voltstack-cluster-active-enhanced-firewall-policies-enhanced-firewall-policies-tenant"></a>&#x2022; [`tenant`](#voltstack-cluster-active-enhanced-firewall-policies-enhanced-firewall-policies-tenant) - Optional String<br>Tenant. When a configuration object(e.g. virtual_host) refers to another(e.g route) then tenant will hold the referred object's(e.g. route's) tenant
+
+#### Voltstack Cluster Active Forward Proxy Policies
+
+An [`active_forward_proxy_policies`](#voltstack-cluster-active-forward-proxy-policies) block (within [`voltstack_cluster`](#voltstack-cluster)) supports the following:
+
+<a id="voltstack-cluster-active-forward-proxy-policies-forward-proxy-policies"></a>&#x2022; [`forward_proxy_policies`](#voltstack-cluster-active-forward-proxy-policies-forward-proxy-policies) - Optional Block<br>Forward Proxy Policies. Ordered List of Forward Proxy Policies active<br>See [Forward Proxy Policies](#voltstack-cluster-active-forward-proxy-policies-forward-proxy-policies) below.
+
+#### Voltstack Cluster Active Forward Proxy Policies Forward Proxy Policies
+
+A [`forward_proxy_policies`](#voltstack-cluster-active-forward-proxy-policies-forward-proxy-policies) block (within [`voltstack_cluster.active_forward_proxy_policies`](#voltstack-cluster-active-forward-proxy-policies)) supports the following:
+
+<a id="voltstack-cluster-active-forward-proxy-policies-forward-proxy-policies-name"></a>&#x2022; [`name`](#voltstack-cluster-active-forward-proxy-policies-forward-proxy-policies-name) - Optional String<br>Name. When a configuration object(e.g. virtual_host) refers to another(e.g route) then name will hold the referred object's(e.g. route's) name
+
+<a id="voltstack-cluster-active-forward-proxy-policies-forward-proxy-policies-namespace"></a>&#x2022; [`namespace`](#voltstack-cluster-active-forward-proxy-policies-forward-proxy-policies-namespace) - Optional String<br>Namespace. When a configuration object(e.g. virtual_host) refers to another(e.g route) then namespace will hold the referred object's(e.g. route's) namespace
+
+<a id="voltstack-cluster-active-forward-proxy-policies-forward-proxy-policies-tenant"></a>&#x2022; [`tenant`](#voltstack-cluster-active-forward-proxy-policies-forward-proxy-policies-tenant) - Optional String<br>Tenant. When a configuration object(e.g. virtual_host) refers to another(e.g route) then tenant will hold the referred object's(e.g. route's) tenant
+
+#### Voltstack Cluster Active Network Policies
+
+An [`active_network_policies`](#voltstack-cluster-active-network-policies) block (within [`voltstack_cluster`](#voltstack-cluster)) supports the following:
+
+<a id="voltstack-cluster-active-network-policies-network-policies"></a>&#x2022; [`network_policies`](#voltstack-cluster-active-network-policies-network-policies) - Optional Block<br>Firewall Policy. Ordered List of Firewall Policies active for this network firewall<br>See [Network Policies](#voltstack-cluster-active-network-policies-network-policies) below.
+
+#### Voltstack Cluster Active Network Policies Network Policies
+
+A [`network_policies`](#voltstack-cluster-active-network-policies-network-policies) block (within [`voltstack_cluster.active_network_policies`](#voltstack-cluster-active-network-policies)) supports the following:
+
+<a id="voltstack-cluster-active-network-policies-network-policies-name"></a>&#x2022; [`name`](#voltstack-cluster-active-network-policies-network-policies-name) - Optional String<br>Name. When a configuration object(e.g. virtual_host) refers to another(e.g route) then name will hold the referred object's(e.g. route's) name
+
+<a id="voltstack-cluster-active-network-policies-network-policies-namespace"></a>&#x2022; [`namespace`](#voltstack-cluster-active-network-policies-network-policies-namespace) - Optional String<br>Namespace. When a configuration object(e.g. virtual_host) refers to another(e.g route) then namespace will hold the referred object's(e.g. route's) namespace
+
+<a id="voltstack-cluster-active-network-policies-network-policies-tenant"></a>&#x2022; [`tenant`](#voltstack-cluster-active-network-policies-network-policies-tenant) - Optional String<br>Tenant. When a configuration object(e.g. virtual_host) refers to another(e.g route) then tenant will hold the referred object's(e.g. route's) tenant
+
+#### Voltstack Cluster Dc Cluster Group
+
+A [`dc_cluster_group`](#voltstack-cluster-dc-cluster-group) block (within [`voltstack_cluster`](#voltstack-cluster)) supports the following:
+
+<a id="voltstack-cluster-dc-cluster-group-name"></a>&#x2022; [`name`](#voltstack-cluster-dc-cluster-group-name) - Optional String<br>Name. When a configuration object(e.g. virtual_host) refers to another(e.g route) then name will hold the referred object's(e.g. route's) name
+
+<a id="voltstack-cluster-dc-cluster-group-namespace"></a>&#x2022; [`namespace`](#voltstack-cluster-dc-cluster-group-namespace) - Optional String<br>Namespace. When a configuration object(e.g. virtual_host) refers to another(e.g route) then namespace will hold the referred object's(e.g. route's) namespace
+
+<a id="voltstack-cluster-dc-cluster-group-tenant"></a>&#x2022; [`tenant`](#voltstack-cluster-dc-cluster-group-tenant) - Optional String<br>Tenant. When a configuration object(e.g. virtual_host) refers to another(e.g route) then tenant will hold the referred object's(e.g. route's) tenant
+
+#### Voltstack Cluster Global Network List
+
+A [`global_network_list`](#voltstack-cluster-global-network-list) block (within [`voltstack_cluster`](#voltstack-cluster)) supports the following:
+
+<a id="voltstack-cluster-global-network-list-global-network-connections"></a>&#x2022; [`global_network_connections`](#voltstack-cluster-global-network-list-global-network-connections) - Optional Block<br>Global Network Connections. Global network connections<br>See [Global Network Connections](#voltstack-cluster-global-network-list-global-network-connections) below.
+
+#### Voltstack Cluster Global Network List Global Network Connections
+
+A [`global_network_connections`](#voltstack-cluster-global-network-list-global-network-connections) block (within [`voltstack_cluster.global_network_list`](#voltstack-cluster-global-network-list)) supports the following:
+
+<a id="voltstack-cluster-global-network-list-global-network-connections-sli-to-global-dr"></a>&#x2022; [`sli_to_global_dr`](#voltstack-cluster-global-network-list-global-network-connections-sli-to-global-dr) - Optional Block<br>Global Network. Global network reference for direct connection<br>See [SLI To Global DR](#voltstack-cluster-global-network-list-global-network-connections-sli-to-global-dr) below.
+
+<a id="voltstack-cluster-global-network-list-global-network-connections-slo-to-global-dr"></a>&#x2022; [`slo_to_global_dr`](#voltstack-cluster-global-network-list-global-network-connections-slo-to-global-dr) - Optional Block<br>Global Network. Global network reference for direct connection<br>See [Slo To Global DR](#voltstack-cluster-global-network-list-global-network-connections-slo-to-global-dr) below.
+
+#### Voltstack Cluster Global Network List Global Network Connections SLI To Global DR
+
+A [`sli_to_global_dr`](#voltstack-cluster-global-network-list-global-network-connections-sli-to-global-dr) block (within [`voltstack_cluster.global_network_list.global_network_connections`](#voltstack-cluster-global-network-list-global-network-connections)) supports the following:
+
+<a id="voltstack-cluster-global-network-list-global-network-connections-sli-to-global-dr-global-vn"></a>&#x2022; [`global_vn`](#voltstack-cluster-global-network-list-global-network-connections-sli-to-global-dr-global-vn) - Optional Block<br>Object reference. This type establishes a direct reference from one object(the referrer) to another(the referred). Such a reference is in form of tenant/namespace/name<br>See [Global Vn](#voltstack-cluster-global-network-list-global-network-connections-sli-to-global-dr-global-vn) below.
+
+#### Voltstack Cluster Global Network List Global Network Connections SLI To Global DR Global Vn
+
+A [`global_vn`](#voltstack-cluster-global-network-list-global-network-connections-sli-to-global-dr-global-vn) block (within [`voltstack_cluster.global_network_list.global_network_connections.sli_to_global_dr`](#voltstack-cluster-global-network-list-global-network-connections-sli-to-global-dr)) supports the following:
+
+<a id="voltstack-cluster-global-network-list-global-network-connections-sli-to-global-dr-global-vn-name"></a>&#x2022; [`name`](#voltstack-cluster-global-network-list-global-network-connections-sli-to-global-dr-global-vn-name) - Optional String<br>Name. When a configuration object(e.g. virtual_host) refers to another(e.g route) then name will hold the referred object's(e.g. route's) name
+
+<a id="voltstack-cluster-global-network-list-global-network-connections-sli-to-global-dr-global-vn-namespace"></a>&#x2022; [`namespace`](#voltstack-cluster-global-network-list-global-network-connections-sli-to-global-dr-global-vn-namespace) - Optional String<br>Namespace. When a configuration object(e.g. virtual_host) refers to another(e.g route) then namespace will hold the referred object's(e.g. route's) namespace
+
+<a id="voltstack-cluster-global-network-list-global-network-connections-sli-to-global-dr-global-vn-tenant"></a>&#x2022; [`tenant`](#voltstack-cluster-global-network-list-global-network-connections-sli-to-global-dr-global-vn-tenant) - Optional String<br>Tenant. When a configuration object(e.g. virtual_host) refers to another(e.g route) then tenant will hold the referred object's(e.g. route's) tenant
+
+#### Voltstack Cluster Global Network List Global Network Connections Slo To Global DR
+
+A [`slo_to_global_dr`](#voltstack-cluster-global-network-list-global-network-connections-slo-to-global-dr) block (within [`voltstack_cluster.global_network_list.global_network_connections`](#voltstack-cluster-global-network-list-global-network-connections)) supports the following:
+
+<a id="voltstack-cluster-global-network-list-global-network-connections-slo-to-global-dr-global-vn"></a>&#x2022; [`global_vn`](#voltstack-cluster-global-network-list-global-network-connections-slo-to-global-dr-global-vn) - Optional Block<br>Object reference. This type establishes a direct reference from one object(the referrer) to another(the referred). Such a reference is in form of tenant/namespace/name<br>See [Global Vn](#voltstack-cluster-global-network-list-global-network-connections-slo-to-global-dr-global-vn) below.
+
+#### Voltstack Cluster Global Network List Global Network Connections Slo To Global DR Global Vn
+
+A [`global_vn`](#voltstack-cluster-global-network-list-global-network-connections-slo-to-global-dr-global-vn) block (within [`voltstack_cluster.global_network_list.global_network_connections.slo_to_global_dr`](#voltstack-cluster-global-network-list-global-network-connections-slo-to-global-dr)) supports the following:
+
+<a id="voltstack-cluster-global-network-list-global-network-connections-slo-to-global-dr-global-vn-name"></a>&#x2022; [`name`](#voltstack-cluster-global-network-list-global-network-connections-slo-to-global-dr-global-vn-name) - Optional String<br>Name. When a configuration object(e.g. virtual_host) refers to another(e.g route) then name will hold the referred object's(e.g. route's) name
+
+<a id="voltstack-cluster-global-network-list-global-network-connections-slo-to-global-dr-global-vn-namespace"></a>&#x2022; [`namespace`](#voltstack-cluster-global-network-list-global-network-connections-slo-to-global-dr-global-vn-namespace) - Optional String<br>Namespace. When a configuration object(e.g. virtual_host) refers to another(e.g route) then namespace will hold the referred object's(e.g. route's) namespace
+
+<a id="voltstack-cluster-global-network-list-global-network-connections-slo-to-global-dr-global-vn-tenant"></a>&#x2022; [`tenant`](#voltstack-cluster-global-network-list-global-network-connections-slo-to-global-dr-global-vn-tenant) - Optional String<br>Tenant. When a configuration object(e.g. virtual_host) refers to another(e.g route) then tenant will hold the referred object's(e.g. route's) tenant
+
+#### Voltstack Cluster K8S Cluster
+
+A [`k8s_cluster`](#voltstack-cluster-k8s-cluster) block (within [`voltstack_cluster`](#voltstack-cluster)) supports the following:
+
+<a id="voltstack-cluster-k8s-cluster-name"></a>&#x2022; [`name`](#voltstack-cluster-k8s-cluster-name) - Optional String<br>Name. When a configuration object(e.g. virtual_host) refers to another(e.g route) then name will hold the referred object's(e.g. route's) name
+
+<a id="voltstack-cluster-k8s-cluster-namespace"></a>&#x2022; [`namespace`](#voltstack-cluster-k8s-cluster-namespace) - Optional String<br>Namespace. When a configuration object(e.g. virtual_host) refers to another(e.g route) then namespace will hold the referred object's(e.g. route's) namespace
+
+<a id="voltstack-cluster-k8s-cluster-tenant"></a>&#x2022; [`tenant`](#voltstack-cluster-k8s-cluster-tenant) - Optional String<br>Tenant. When a configuration object(e.g. virtual_host) refers to another(e.g route) then tenant will hold the referred object's(e.g. route's) tenant
+
+#### Voltstack Cluster Outside Static Routes
+
+An [`outside_static_routes`](#voltstack-cluster-outside-static-routes) block (within [`voltstack_cluster`](#voltstack-cluster)) supports the following:
+
+<a id="voltstack-cluster-outside-static-routes-static-route-list"></a>&#x2022; [`static_route_list`](#voltstack-cluster-outside-static-routes-static-route-list) - Optional Block<br>List of Static Routes. List of Static routes<br>See [Static Route List](#voltstack-cluster-outside-static-routes-static-route-list) below.
+
+#### Voltstack Cluster Outside Static Routes Static Route List
+
+A [`static_route_list`](#voltstack-cluster-outside-static-routes-static-route-list) block (within [`voltstack_cluster.outside_static_routes`](#voltstack-cluster-outside-static-routes)) supports the following:
+
+<a id="voltstack-cluster-outside-static-routes-static-route-list-custom-static-route"></a>&#x2022; [`custom_static_route`](#voltstack-cluster-outside-static-routes-static-route-list-custom-static-route) - Optional Block<br>Static Route. Defines a static route, configuring a list of prefixes and a next-hop to be used for them<br>See [Custom Static Route](#voltstack-cluster-outside-static-routes-static-route-list-custom-static-route) below.
+
+<a id="voltstack-cluster-outside-static-routes-static-route-list-simple-static-route"></a>&#x2022; [`simple_static_route`](#voltstack-cluster-outside-static-routes-static-route-list-simple-static-route) - Optional String<br>Simple Static Route. Use simple static route for prefix pointing to single interface in the network
+
+#### Voltstack Cluster Outside Static Routes Static Route List Custom Static Route
+
+A [`custom_static_route`](#voltstack-cluster-outside-static-routes-static-route-list-custom-static-route) block (within [`voltstack_cluster.outside_static_routes.static_route_list`](#voltstack-cluster-outside-static-routes-static-route-list)) supports the following:
+
+<a id="voltstack-cluster-outside-static-routes-static-route-list-custom-static-route-attrs"></a>&#x2022; [`attrs`](#voltstack-cluster-outside-static-routes-static-route-list-custom-static-route-attrs) - Optional List  Defaults to `ROUTE_ATTR_NO_OP`<br>Possible values are `ROUTE_ATTR_NO_OP`, `ROUTE_ATTR_ADVERTISE`, `ROUTE_ATTR_INSTALL_HOST`, `ROUTE_ATTR_INSTALL_FORWARDING`, `ROUTE_ATTR_MERGE_ONLY`<br>[Enum: ROUTE_ATTR_NO_OP|ROUTE_ATTR_ADVERTISE|ROUTE_ATTR_INSTALL_HOST|ROUTE_ATTR_INSTALL_FORWARDING|ROUTE_ATTR_MERGE_ONLY] Attributes. List of route attributes associated with the static route
+
+<a id="voltstack-cluster-outside-static-routes-static-route-list-custom-static-route-labels"></a>&#x2022; [`labels`](#voltstack-cluster-outside-static-routes-static-route-list-custom-static-route-labels) - Optional Block<br>Static Route Labels. Add Labels for this Static Route, these labels can be used in network policy
+
+<a id="voltstack-cluster-outside-static-routes-static-route-list-custom-static-route-nexthop"></a>&#x2022; [`nexthop`](#voltstack-cluster-outside-static-routes-static-route-list-custom-static-route-nexthop) - Optional Block<br>Nexthop. Identifies the next-hop for a route<br>See [Nexthop](#voltstack-cluster-outside-static-routes-static-route-list-custom-static-route-nexthop) below.
+
+<a id="voltstack-cluster-outside-static-routes-static-route-list-custom-static-route-subnets"></a>&#x2022; [`subnets`](#voltstack-cluster-outside-static-routes-static-route-list-custom-static-route-subnets) - Optional Block<br>Subnets. List of route prefixes<br>See [Subnets](#voltstack-cluster-outside-static-routes-static-route-list-custom-static-route-subnets) below.
+
+#### Voltstack Cluster Outside Static Routes Static Route List Custom Static Route Nexthop
+
+A [`nexthop`](#voltstack-cluster-outside-static-routes-static-route-list-custom-static-route-nexthop) block (within [`voltstack_cluster.outside_static_routes.static_route_list.custom_static_route`](#voltstack-cluster-outside-static-routes-static-route-list-custom-static-route)) supports the following:
+
+<a id="voltstack-cluster-outside-static-routes-static-route-list-custom-static-route-nexthop-interface"></a>&#x2022; [`interface`](#voltstack-cluster-outside-static-routes-static-route-list-custom-static-route-nexthop-interface) - Optional Block<br>Network Interface. Nexthop is network interface when type is 'Network-Interface'<br>See [Interface](#voltstack-cluster-outside-static-routes-static-route-list-custom-static-route-nexthop-interface) below.
+
+<a id="voltstack-cluster-outside-static-routes-static-route-list-custom-static-route-nexthop-nexthop-address"></a>&#x2022; [`nexthop_address`](#voltstack-cluster-outside-static-routes-static-route-list-custom-static-route-nexthop-nexthop-address) - Optional Block<br>IP Address. IP Address used to specify an IPv4 or IPv6 address<br>See [Nexthop Address](#voltstack-cluster-outside-static-routes-static-route-list-custom-static-route-nexthop-nexthop-address) below.
+
+<a id="voltstack-cluster-outside-static-routes-static-route-list-custom-static-route-nexthop-type"></a>&#x2022; [`type`](#voltstack-cluster-outside-static-routes-static-route-list-custom-static-route-nexthop-type) - Optional String  Defaults to `NEXT_HOP_DEFAULT_GATEWAY`<br>Possible values are `NEXT_HOP_DEFAULT_GATEWAY`, `NEXT_HOP_USE_CONFIGURED`, `NEXT_HOP_NETWORK_INTERFACE`<br>[Enum: NEXT_HOP_DEFAULT_GATEWAY|NEXT_HOP_USE_CONFIGURED|NEXT_HOP_NETWORK_INTERFACE] Nexthop Types. Defines types of next-hop Use default gateway on the local interface as gateway for route. Assumes there is only one local interface on the virtual network. Use the specified address as nexthop Use the network interface as nexthop Discard nexthop, used when attr type is Advertise Used in VoltADN private virtual network
+
+#### Voltstack Cluster Outside Static Routes Static Route List Custom Static Route Nexthop Interface
+
+An [`interface`](#voltstack-cluster-outside-static-routes-static-route-list-custom-static-route-nexthop-interface) block (within [`voltstack_cluster.outside_static_routes.static_route_list.custom_static_route.nexthop`](#voltstack-cluster-outside-static-routes-static-route-list-custom-static-route-nexthop)) supports the following:
+
+<a id="voltstack-cluster-outside-static-routes-static-route-list-custom-static-route-nexthop-interface-kind"></a>&#x2022; [`kind`](#voltstack-cluster-outside-static-routes-static-route-list-custom-static-route-nexthop-interface-kind) - Optional String<br>Kind. When a configuration object(e.g. virtual_host) refers to another(e.g route) then kind will hold the referred object's kind (e.g. 'route')
+
+<a id="voltstack-cluster-outside-static-routes-static-route-list-custom-static-route-nexthop-interface-name"></a>&#x2022; [`name`](#voltstack-cluster-outside-static-routes-static-route-list-custom-static-route-nexthop-interface-name) - Optional String<br>Name. When a configuration object(e.g. virtual_host) refers to another(e.g route) then name will hold the referred object's(e.g. route's) name
+
+<a id="voltstack-cluster-outside-static-routes-static-route-list-custom-static-route-nexthop-interface-namespace"></a>&#x2022; [`namespace`](#voltstack-cluster-outside-static-routes-static-route-list-custom-static-route-nexthop-interface-namespace) - Optional String<br>Namespace. When a configuration object(e.g. virtual_host) refers to another(e.g route) then namespace will hold the referred object's(e.g. route's) namespace
+
+<a id="voltstack-cluster-outside-static-routes-static-route-list-custom-static-route-nexthop-interface-tenant"></a>&#x2022; [`tenant`](#voltstack-cluster-outside-static-routes-static-route-list-custom-static-route-nexthop-interface-tenant) - Optional String<br>Tenant. When a configuration object(e.g. virtual_host) refers to another(e.g route) then tenant will hold the referred object's(e.g. route's) tenant
+
+<a id="voltstack-cluster-outside-static-routes-static-route-list-custom-static-route-nexthop-interface-uid"></a>&#x2022; [`uid`](#voltstack-cluster-outside-static-routes-static-route-list-custom-static-route-nexthop-interface-uid) - Optional String<br>UID. When a configuration object(e.g. virtual_host) refers to another(e.g route) then uid will hold the referred object's(e.g. route's) uid
+
+#### Voltstack Cluster Outside Static Routes Static Route List Custom Static Route Nexthop Nexthop Address
+
+A [`nexthop_address`](#voltstack-cluster-outside-static-routes-static-route-list-custom-static-route-nexthop-nexthop-address) block (within [`voltstack_cluster.outside_static_routes.static_route_list.custom_static_route.nexthop`](#voltstack-cluster-outside-static-routes-static-route-list-custom-static-route-nexthop)) supports the following:
+
+<a id="voltstack-cluster-outside-static-routes-static-route-list-custom-static-route-nexthop-nexthop-address-ipv4"></a>&#x2022; [`ipv4`](#voltstack-cluster-outside-static-routes-static-route-list-custom-static-route-nexthop-nexthop-address-ipv4) - Optional Block<br>IPv4 Address. IPv4 Address in dot-decimal notation<br>See [IPv4](#voltstack-cluster-outside-static-routes-static-route-list-custom-static-route-nexthop-nexthop-address-ipv4) below.
+
+<a id="voltstack-cluster-outside-static-routes-static-route-list-custom-static-route-nexthop-nexthop-address-ipv6"></a>&#x2022; [`ipv6`](#voltstack-cluster-outside-static-routes-static-route-list-custom-static-route-nexthop-nexthop-address-ipv6) - Optional Block<br>IPv6 Address. IPv6 Address specified as hexadecimal numbers separated by ':'<br>See [IPv6](#voltstack-cluster-outside-static-routes-static-route-list-custom-static-route-nexthop-nexthop-address-ipv6) below.
+
+#### Voltstack Cluster Outside Static Routes Static Route List Custom Static Route Nexthop Nexthop Address IPv4
+
+An [`ipv4`](#voltstack-cluster-outside-static-routes-static-route-list-custom-static-route-nexthop-nexthop-address-ipv4) block (within [`voltstack_cluster.outside_static_routes.static_route_list.custom_static_route.nexthop.nexthop_address`](#voltstack-cluster-outside-static-routes-static-route-list-custom-static-route-nexthop-nexthop-address)) supports the following:
+
+<a id="voltstack-cluster-outside-static-routes-static-route-list-custom-static-route-nexthop-nexthop-address-ipv4-addr"></a>&#x2022; [`addr`](#voltstack-cluster-outside-static-routes-static-route-list-custom-static-route-nexthop-nexthop-address-ipv4-addr) - Optional String<br>IPv4 Address. IPv4 Address in string form with dot-decimal notation
+
+#### Voltstack Cluster Outside Static Routes Static Route List Custom Static Route Nexthop Nexthop Address IPv6
+
+An [`ipv6`](#voltstack-cluster-outside-static-routes-static-route-list-custom-static-route-nexthop-nexthop-address-ipv6) block (within [`voltstack_cluster.outside_static_routes.static_route_list.custom_static_route.nexthop.nexthop_address`](#voltstack-cluster-outside-static-routes-static-route-list-custom-static-route-nexthop-nexthop-address)) supports the following:
+
+<a id="voltstack-cluster-outside-static-routes-static-route-list-custom-static-route-nexthop-nexthop-address-ipv6-addr"></a>&#x2022; [`addr`](#voltstack-cluster-outside-static-routes-static-route-list-custom-static-route-nexthop-nexthop-address-ipv6-addr) - Optional String<br>IPv6 Address. IPv6 Address in form of string. IPv6 address must be specified as hexadecimal numbers separated by ':' The address can be compacted by suppressing zeros e.g. '2001:db8:0:0:0:0:2:1' becomes '2001:db8::2:1' or '2001:db8:0:0:0:2:0:0' becomes '2001:db8::2::'
+
+#### Voltstack Cluster Outside Static Routes Static Route List Custom Static Route Subnets
+
+A [`subnets`](#voltstack-cluster-outside-static-routes-static-route-list-custom-static-route-subnets) block (within [`voltstack_cluster.outside_static_routes.static_route_list.custom_static_route`](#voltstack-cluster-outside-static-routes-static-route-list-custom-static-route)) supports the following:
+
+<a id="voltstack-cluster-outside-static-routes-static-route-list-custom-static-route-subnets-ipv4"></a>&#x2022; [`ipv4`](#voltstack-cluster-outside-static-routes-static-route-list-custom-static-route-subnets-ipv4) - Optional Block<br>IPv4 Subnet. IPv4 subnets specified as prefix and prefix-length. Prefix length must be <= 32<br>See [IPv4](#voltstack-cluster-outside-static-routes-static-route-list-custom-static-route-subnets-ipv4) below.
+
+<a id="voltstack-cluster-outside-static-routes-static-route-list-custom-static-route-subnets-ipv6"></a>&#x2022; [`ipv6`](#voltstack-cluster-outside-static-routes-static-route-list-custom-static-route-subnets-ipv6) - Optional Block<br>IPv6 Subnet. IPv6 subnets specified as prefix and prefix-length. prefix-legnth must be <= 128<br>See [IPv6](#voltstack-cluster-outside-static-routes-static-route-list-custom-static-route-subnets-ipv6) below.
+
+#### Voltstack Cluster Outside Static Routes Static Route List Custom Static Route Subnets IPv4
+
+An [`ipv4`](#voltstack-cluster-outside-static-routes-static-route-list-custom-static-route-subnets-ipv4) block (within [`voltstack_cluster.outside_static_routes.static_route_list.custom_static_route.subnets`](#voltstack-cluster-outside-static-routes-static-route-list-custom-static-route-subnets)) supports the following:
+
+<a id="voltstack-cluster-outside-static-routes-static-route-list-custom-static-route-subnets-ipv4-plen"></a>&#x2022; [`plen`](#voltstack-cluster-outside-static-routes-static-route-list-custom-static-route-subnets-ipv4-plen) - Optional Number<br>Prefix Length. Prefix-length of the IPv4 subnet. Must be <= 32
+
+<a id="voltstack-cluster-outside-static-routes-static-route-list-custom-static-route-subnets-ipv4-prefix"></a>&#x2022; [`prefix`](#voltstack-cluster-outside-static-routes-static-route-list-custom-static-route-subnets-ipv4-prefix) - Optional String<br>Prefix. Prefix part of the IPv4 subnet in string form with dot-decimal notation
+
+#### Voltstack Cluster Outside Static Routes Static Route List Custom Static Route Subnets IPv6
+
+An [`ipv6`](#voltstack-cluster-outside-static-routes-static-route-list-custom-static-route-subnets-ipv6) block (within [`voltstack_cluster.outside_static_routes.static_route_list.custom_static_route.subnets`](#voltstack-cluster-outside-static-routes-static-route-list-custom-static-route-subnets)) supports the following:
+
+<a id="voltstack-cluster-outside-static-routes-static-route-list-custom-static-route-subnets-ipv6-plen"></a>&#x2022; [`plen`](#voltstack-cluster-outside-static-routes-static-route-list-custom-static-route-subnets-ipv6-plen) - Optional Number<br>Prefix Length. Prefix length of the IPv6 subnet. Must be <= 128
+
+<a id="voltstack-cluster-outside-static-routes-static-route-list-custom-static-route-subnets-ipv6-prefix"></a>&#x2022; [`prefix`](#voltstack-cluster-outside-static-routes-static-route-list-custom-static-route-subnets-ipv6-prefix) - Optional String<br>Prefix. Prefix part of the IPv6 subnet given in form of string. IPv6 address must be specified as hexadecimal numbers separated by ':' e.g. '2001:db8:0:0:0:2:0:0' The address can be compacted by suppressing zeros e.g. '2001:db8::2::'
+
+#### Voltstack Cluster Site Local Network
+
+A [`site_local_network`](#voltstack-cluster-site-local-network) block (within [`voltstack_cluster`](#voltstack-cluster)) supports the following:
+
+<a id="voltstack-cluster-site-local-network-existing-network"></a>&#x2022; [`existing_network`](#voltstack-cluster-site-local-network-existing-network) - Optional Block<br>GCP existing VPC network Type. Name of existing VPC network<br>See [Existing Network](#voltstack-cluster-site-local-network-existing-network) below.
+
+<a id="voltstack-cluster-site-local-network-new-network"></a>&#x2022; [`new_network`](#voltstack-cluster-site-local-network-new-network) - Optional Block<br>GCP VPC Network Manual Parameters. Parameters to create a new GCP VPC Network<br>See [New Network](#voltstack-cluster-site-local-network-new-network) below.
+
+<a id="voltstack-cluster-site-local-network-new-network-autogenerate"></a>&#x2022; [`new_network_autogenerate`](#voltstack-cluster-site-local-network-new-network-autogenerate) - Optional Block<br>GCP VPC Network Autogenerated Parameters. Create a new GCP VPC Network with autogenerated name
+
+#### Voltstack Cluster Site Local Network Existing Network
+
+An [`existing_network`](#voltstack-cluster-site-local-network-existing-network) block (within [`voltstack_cluster.site_local_network`](#voltstack-cluster-site-local-network)) supports the following:
+
+<a id="voltstack-cluster-site-local-network-existing-network-name"></a>&#x2022; [`name`](#voltstack-cluster-site-local-network-existing-network-name) - Optional String<br>GCP VPC Network Name. Name for your GCP VPC Network
+
+#### Voltstack Cluster Site Local Network New Network
+
+A [`new_network`](#voltstack-cluster-site-local-network-new-network) block (within [`voltstack_cluster.site_local_network`](#voltstack-cluster-site-local-network)) supports the following:
+
+<a id="voltstack-cluster-site-local-network-new-network-name"></a>&#x2022; [`name`](#voltstack-cluster-site-local-network-new-network-name) - Optional String<br>GCP VPC Network Name. Name for your GCP VPC Network
+
+#### Voltstack Cluster Site Local Subnet
+
+A [`site_local_subnet`](#voltstack-cluster-site-local-subnet) block (within [`voltstack_cluster`](#voltstack-cluster)) supports the following:
+
+<a id="voltstack-cluster-site-local-subnet-existing-subnet"></a>&#x2022; [`existing_subnet`](#voltstack-cluster-site-local-subnet-existing-subnet) - Optional Block<br>GCP existing subnet Type. Name of existing GCP subnet<br>See [Existing Subnet](#voltstack-cluster-site-local-subnet-existing-subnet) below.
+
+<a id="voltstack-cluster-site-local-subnet-new-subnet"></a>&#x2022; [`new_subnet`](#voltstack-cluster-site-local-subnet-new-subnet) - Optional Block<br>GCP subnet parameters Type. Parameters for GCP subnet<br>See [New Subnet](#voltstack-cluster-site-local-subnet-new-subnet) below.
+
+#### Voltstack Cluster Site Local Subnet Existing Subnet
+
+An [`existing_subnet`](#voltstack-cluster-site-local-subnet-existing-subnet) block (within [`voltstack_cluster.site_local_subnet`](#voltstack-cluster-site-local-subnet)) supports the following:
+
+<a id="voltstack-cluster-site-local-subnet-existing-subnet-subnet-name"></a>&#x2022; [`subnet_name`](#voltstack-cluster-site-local-subnet-existing-subnet-subnet-name) - Optional String<br>VPC Subnet Name. Name of your subnet in VPC network
+
+#### Voltstack Cluster Site Local Subnet New Subnet
+
+A [`new_subnet`](#voltstack-cluster-site-local-subnet-new-subnet) block (within [`voltstack_cluster.site_local_subnet`](#voltstack-cluster-site-local-subnet)) supports the following:
+
+<a id="voltstack-cluster-site-local-subnet-new-subnet-primary-ipv4"></a>&#x2022; [`primary_ipv4`](#voltstack-cluster-site-local-subnet-new-subnet-primary-ipv4) - Optional String<br>IPv4 Subnet Prefix. IPv4 prefix for this Subnet. It has to be private address space
+
+<a id="voltstack-cluster-site-local-subnet-new-subnet-subnet-name"></a>&#x2022; [`subnet_name`](#voltstack-cluster-site-local-subnet-new-subnet-subnet-name) - Optional String<br>VPC Subnet Name. Name of new VPC Subnet, will be autogenerated if empty
+
+#### Voltstack Cluster Storage Class List
+
+A [`storage_class_list`](#voltstack-cluster-storage-class-list) block (within [`voltstack_cluster`](#voltstack-cluster)) supports the following:
+
+<a id="voltstack-cluster-storage-class-list-storage-classes"></a>&#x2022; [`storage_classes`](#voltstack-cluster-storage-class-list-storage-classes) - Optional Block<br>List of Storage Classes. List of custom storage classes<br>See [Storage Classes](#voltstack-cluster-storage-class-list-storage-classes) below.
+
+#### Voltstack Cluster Storage Class List Storage Classes
+
+A [`storage_classes`](#voltstack-cluster-storage-class-list-storage-classes) block (within [`voltstack_cluster.storage_class_list`](#voltstack-cluster-storage-class-list)) supports the following:
+
+<a id="voltstack-cluster-storage-class-list-storage-classes-default-storage-class"></a>&#x2022; [`default_storage_class`](#voltstack-cluster-storage-class-list-storage-classes-default-storage-class) - Optional Bool<br>Default Storage Class. Make this storage class default storage class for the K8S cluster
+
+<a id="voltstack-cluster-storage-class-list-storage-classes-storage-class-name"></a>&#x2022; [`storage_class_name`](#voltstack-cluster-storage-class-list-storage-classes-storage-class-name) - Optional String<br>Storage Class Name. Name of the storage class as it will appear in K8S
+
+## Import
+
+Import is supported using the following syntax:
+
+```shell
+# Import using namespace/name format
+terraform import f5xc_gcp_vpc_site.example system/example
+```