@robinmordasiewicz/f5xc-terraform-mcp 2.3.0 → 2.4.3

package/dist/docs/resources/tcp_loadbalancer.md

@@ -0,0 +1,671 @@
+---
+page_title: "f5xc_tcp_loadbalancer Resource - terraform-provider-f5xc"
+subcategory: "Load Balancing"
+description: |-
+  [Category: Load Balancing] [Namespace: required] [DependsOn: namespace, origin_pool] Manages a TCP Load Balancer resource in F5 Distributed Cloud for load balancing TCP traffic across origin pools.
+---
+
+# f5xc_tcp_loadbalancer (Resource)
+
+[Category: Load Balancing] [Namespace: required] [DependsOn: namespace, origin_pool] Manages a TCP Load Balancer resource in F5 Distributed Cloud for load balancing TCP traffic across origin pools.
+
+~> **Note** Please refer to [TCP Loadbalancer API docs](https://docs.cloud.f5.com/docs-v2/api/views-tcp-loadbalancer) to learn more.
+
+## Example Usage
+
+```terraform
+# TCP Loadbalancer Resource Example
+# [Category: Load Balancing] [Namespace: required] [DependsOn: namespace, origin_pool] Manages a TCP Load Balancer resource in F5 Distributed Cloud for load balancing TCP traffic across origin pools.
+
+# Basic TCP Loadbalancer configuration
+resource "f5xc_tcp_loadbalancer" "example" {
+  name      = "example-tcp-loadbalancer"
+  namespace = "staging"
+
+  labels = {
+    environment = "production"
+    managed_by  = "terraform"
+  }
+
+  annotations = {
+    "owner" = "platform-team"
+  }
+
+  # TCP Load Balancer specific configuration
+  listen_port = 8443
+
+  # Advertise on public internet
+  advertise_on_internet {
+    default_vip {}
+  }
+
+  # Origin pools
+  origin_pools_weights {
+    pool {
+      name      = "example-tcp-pool"
+      namespace = "staging"
+    }
+    weight = 1
+  }
+
+  # DNS for TCP load balancer
+  dns_volterra_managed = true
+
+  # No retract cluster by default
+  retract_cluster {}
+}
+```
+
+<!-- schema generated by tfplugindocs -->
+## Argument Reference
+
+### Metadata Argument Reference
+
+<a id="name"></a>&#x2022; [`name`](#name) - Required String<br>Name of the TCP Load Balancer. Must be unique within the namespace
+
+<a id="namespace"></a>&#x2022; [`namespace`](#namespace) - Required String<br>Namespace where the TCP Load Balancer 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
+
+-> **One of the following:**
+&#x2022; <a id="active-service-policies"></a>[`active_service_policies`](#active-service-policies) - Optional Block<br>Service Policy List. List of service policies<br>See [Active Service Policies](#active-service-policies) below for details.
+<br><br>&#x2022; <a id="no-service-policies"></a>[`no_service_policies`](#no-service-policies) - Optional Block<br>Enable this option
+
+-> **One of the following:**
+&#x2022; <a id="advertise-custom"></a>[`advertise_custom`](#advertise-custom) - Optional Block<br>Advertise Custom. This defines a way to advertise a VIP on specific sites<br>See [Advertise Custom](#advertise-custom) below for details.
+<br><br>&#x2022; <a id="advertise-on-public"></a>[`advertise_on_public`](#advertise-on-public) - Optional Block<br>Advertise Public. This defines a way to advertise a load balancer on public. If optional public_ip is provided, it will only be advertised on RE sites where that public_ip is available<br>See [Advertise On Public](#advertise-on-public) below for details.
+<br><br>&#x2022; <a id="advertise-on-public-default-vip"></a>[`advertise_on_public_default_vip`](#advertise-on-public-default-vip) - Optional Block<br>Enable this option
+
+-> **One of the following:**
+&#x2022; <a id="default-lb-with-sni"></a>[`default_lb_with_sni`](#default-lb-with-sni) - Optional Block<br>Enable this option
+<br><br>&#x2022; <a id="no-sni"></a>[`no_sni`](#no-sni) - Optional Block<br>Enable this option
+
+<a id="dns-volterra-managed"></a>&#x2022; [`dns_volterra_managed`](#dns-volterra-managed) - Optional Bool<br>Automatically Manage DNS Records. DNS records for domains will be managed automatically by Volterra. This requires the domain to be delegated to F5XC using the Delegated Domain feature
+
+<a id="do-not-advertise"></a>&#x2022; [`do_not_advertise`](#do-not-advertise) - Optional Block<br>Enable this option
+
+-> **One of the following:**
+&#x2022; <a id="do-not-retract-cluster"></a>[`do_not_retract_cluster`](#do-not-retract-cluster) - Optional Block<br>Enable this option
+<br><br>&#x2022; <a id="retract-cluster"></a>[`retract_cluster`](#retract-cluster) - Optional Block<br>Enable this option
+
+<a id="domains"></a>&#x2022; [`domains`](#domains) - Optional List<br>Domains. A list of Domains (host/authority header) that will be matched to this Load Balancer. Supported Domains and search order: 1. Exact Domain names: `www.foo.com.` 2. Domains starting with a Wildcard: \*.foo.com. Not supported Domains: - Just a Wildcard: \* - A Wildcard and TLD with no root Domain: \*.com. - A Wildcard not matching a whole DNS label. e.g. \*.foo.com and \*.bar.foo.com are valid Wildcards however \*bar.foo.com, \*-bar.foo.com, and bar*.foo.com are all invalid. Additional notes: A Wildcard will not match empty string. e.g. \*.foo.com will match bar.foo.com and baz-bar.foo.com but not .foo.com. The longest Wildcards match first. Only a single virtual host in the entire route configuration can match on \*. Also a Domain must be unique across all virtual hosts within an advertise policy. Domains are also used for SNI matching if SNI is activated on the given TCP Load Balancer. Domains also indicate the list of names for which DNS resolution will be automatically resolved to IP addresses by the system
+
+-> **One of the following:**
+&#x2022; <a id="hash-policy-choice-least-active"></a>[`hash_policy_choice_least_active`](#hash-policy-choice-least-active) - Optional Block<br>Enable this option
+<br><br>&#x2022; <a id="hash-policy-choice-random"></a>[`hash_policy_choice_random`](#hash-policy-choice-random) - Optional Block<br>Enable this option
+<br><br>&#x2022; <a id="hash-policy-choice-round-robin"></a>[`hash_policy_choice_round_robin`](#hash-policy-choice-round-robin) - Optional Block<br>Enable this option
+<br><br>&#x2022; <a id="hash-policy-choice-source-ip-stickiness"></a>[`hash_policy_choice_source_ip_stickiness`](#hash-policy-choice-source-ip-stickiness) - Optional Block<br>Enable this option
+
+<a id="idle-timeout"></a>&#x2022; [`idle_timeout`](#idle-timeout) - Optional Number<br>Idle Timeout. The amount of time that a stream can exist without upstream or downstream activity, in milliseconds
+
+-> **One of the following:**
+&#x2022; <a id="listen-port"></a>[`listen_port`](#listen-port) - Optional Number<br>Listen Port. Listen Port for this load balancer
+<br><br>&#x2022; <a id="port-ranges"></a>[`port_ranges`](#port-ranges) - Optional String<br>Port Ranges. A string containing a comma separated list of port ranges. Each port range consists of a single port or two ports separated by '-'
+
+<a id="origin-pools-weights"></a>&#x2022; [`origin_pools_weights`](#origin-pools-weights) - Optional Block<br>Origin Pools. Origin pools and weights used for this load balancer<br>See [Origin Pools Weights](#origin-pools-weights) below for details.
+
+<a id="service-policies-from-namespace"></a>&#x2022; [`service_policies_from_namespace`](#service-policies-from-namespace) - Optional Block<br>Enable this option
+
+<a id="sni"></a>&#x2022; [`sni`](#sni) - Optional Block<br>Enable this option
+
+-> **One of the following:**
+&#x2022; <a id="tcp"></a>[`tcp`](#tcp) - Optional Block<br>Enable this option
+<br><br>&#x2022; <a id="tls-tcp"></a>[`tls_tcp`](#tls-tcp) - Optional Block<br>BYOC TLS over TCP Choice. Choice for selecting TLS over TCP proxy with bring your own certificates<br>See [TLS TCP](#tls-tcp) below for details.
+<br><br>&#x2022; <a id="tls-tcp-auto-cert"></a>[`tls_tcp_auto_cert`](#tls-tcp-auto-cert) - Optional Block<br>TLS over TCP with Auto Certs Choice. Choice for selecting TLS over TCP proxy with automatic certificates
+
+<a id="timeouts"></a>&#x2022; [`timeouts`](#timeouts) - Optional Block<br>See [Timeouts](#timeouts) below for details.
+
+### 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
+
+---
+
+#### Active Service Policies
+
+An [`active_service_policies`](#active-service-policies) block supports the following:
+
+<a id="active-service-policies-policies"></a>&#x2022; [`policies`](#active-service-policies-policies) - Optional Block<br>Policies. Service Policies is a sequential engine where policies (and rules within the policy) are evaluated one after the other. It's important to define the correct order (policies evaluated from top to bottom in the list) for service policies, to get the intended result. For each request, its characteristics are evaluated based on the match criteria in each service policy starting at the top. If there is a match in the current policy, then the policy takes effect, and no more policies are evaluated. Otherwise, the next policy is evaluated. If all policies are evaluated and none match, then the request will be denied by default<br>See [Policies](#active-service-policies-policies) below.
+
+#### Active Service Policies Policies
+
+A [`policies`](#active-service-policies-policies) block (within [`active_service_policies`](#active-service-policies)) supports the following:
+
+<a id="active-service-policies-policies-name"></a>&#x2022; [`name`](#active-service-policies-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="active-service-policies-policies-namespace"></a>&#x2022; [`namespace`](#active-service-policies-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="active-service-policies-policies-tenant"></a>&#x2022; [`tenant`](#active-service-policies-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
+
+#### Advertise Custom
+
+An [`advertise_custom`](#advertise-custom) block supports the following:
+
+<a id="advertise-custom-advertise-where"></a>&#x2022; [`advertise_where`](#advertise-custom-advertise-where) - Optional Block<br>List of Sites to Advertise. Where should this load balancer be available<br>See [Advertise Where](#advertise-custom-advertise-where) below.
+
+#### Advertise Custom Advertise Where
+
+An [`advertise_where`](#advertise-custom-advertise-where) block (within [`advertise_custom`](#advertise-custom)) supports the following:
+
+<a id="advertise-custom-advertise-where-advertise-on-public"></a>&#x2022; [`advertise_on_public`](#advertise-custom-advertise-where-advertise-on-public) - Optional Block<br>Advertise Public. This defines a way to advertise a load balancer on public. If optional public_ip is provided, it will only be advertised on RE sites where that public_ip is available<br>See [Advertise On Public](#advertise-custom-advertise-where-advertise-on-public) below.
+
+<a id="advertise-custom-advertise-where-port"></a>&#x2022; [`port`](#advertise-custom-advertise-where-port) - Optional Number<br>Listen Port. Port to Listen
+
+<a id="advertise-custom-advertise-where-port-ranges"></a>&#x2022; [`port_ranges`](#advertise-custom-advertise-where-port-ranges) - Optional String<br>Listen Port Ranges. A string containing a comma separated list of port ranges. Each port range consists of a single port or two ports separated by '-'
+
+<a id="advertise-custom-advertise-where-site"></a>&#x2022; [`site`](#advertise-custom-advertise-where-site) - Optional Block<br>Site. This defines a reference to a CE site along with network type and an optional IP address where a load balancer could be advertised<br>See [Site](#advertise-custom-advertise-where-site) below.
+
+<a id="advertise-custom-advertise-where-use-default-port"></a>&#x2022; [`use_default_port`](#advertise-custom-advertise-where-use-default-port) - Optional Block<br>Enable this option
+
+<a id="advertise-custom-advertise-where-virtual-network"></a>&#x2022; [`virtual_network`](#advertise-custom-advertise-where-virtual-network) - Optional Block<br>Virtual Network. Parameters to advertise on a given virtual network<br>See [Virtual Network](#advertise-custom-advertise-where-virtual-network) below.
+
+<a id="advertise-custom-advertise-where-virtual-site"></a>&#x2022; [`virtual_site`](#advertise-custom-advertise-where-virtual-site) - Optional Block<br>Virtual Site. This defines a reference to a customer site virtual site along with network type where a load balancer could be advertised<br>See [Virtual Site](#advertise-custom-advertise-where-virtual-site) below.
+
+<a id="advertise-custom-advertise-where-virtual-site-with-vip"></a>&#x2022; [`virtual_site_with_vip`](#advertise-custom-advertise-where-virtual-site-with-vip) - Optional Block<br>Virtual Site with Specified VIP. This defines a reference to a customer site virtual site along with network type and IP where a load balancer could be advertised<br>See [Virtual Site With VIP](#advertise-custom-advertise-where-virtual-site-with-vip) below.
+
+<a id="advertise-custom-advertise-where-vk8s-service"></a>&#x2022; [`vk8s_service`](#advertise-custom-advertise-where-vk8s-service) - Optional Block<br>vK8s Services on RE. This defines a reference to a RE site or virtual site where a load balancer could be advertised in the vK8s service network<br>See [Vk8s Service](#advertise-custom-advertise-where-vk8s-service) below.
+
+#### Advertise Custom Advertise Where Advertise On Public
+
+An [`advertise_on_public`](#advertise-custom-advertise-where-advertise-on-public) block (within [`advertise_custom.advertise_where`](#advertise-custom-advertise-where)) supports the following:
+
+<a id="advertise-custom-advertise-where-advertise-on-public-public-ip"></a>&#x2022; [`public_ip`](#advertise-custom-advertise-where-advertise-on-public-public-ip) - 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 [Public IP](#advertise-custom-advertise-where-advertise-on-public-public-ip) below.
+
+#### Advertise Custom Advertise Where Advertise On Public Public IP
+
+A [`public_ip`](#advertise-custom-advertise-where-advertise-on-public-public-ip) block (within [`advertise_custom.advertise_where.advertise_on_public`](#advertise-custom-advertise-where-advertise-on-public)) supports the following:
+
+<a id="advertise-custom-advertise-where-advertise-on-public-public-ip-name"></a>&#x2022; [`name`](#advertise-custom-advertise-where-advertise-on-public-public-ip-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="advertise-custom-advertise-where-advertise-on-public-public-ip-namespace"></a>&#x2022; [`namespace`](#advertise-custom-advertise-where-advertise-on-public-public-ip-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="advertise-custom-advertise-where-advertise-on-public-public-ip-tenant"></a>&#x2022; [`tenant`](#advertise-custom-advertise-where-advertise-on-public-public-ip-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
+
+#### Advertise Custom Advertise Where Site
+
+A [`site`](#advertise-custom-advertise-where-site) block (within [`advertise_custom.advertise_where`](#advertise-custom-advertise-where)) supports the following:
+
+<a id="advertise-custom-advertise-where-site-ip"></a>&#x2022; [`ip`](#advertise-custom-advertise-where-site-ip) - Optional String<br>IP Address. Use given IP address as VIP on the site
+
+<a id="advertise-custom-advertise-where-site-network"></a>&#x2022; [`network`](#advertise-custom-advertise-where-site-network) - Optional String  Defaults to `SITE_NETWORK_INSIDE_AND_OUTSIDE`<br>Possible values are `SITE_NETWORK_INSIDE_AND_OUTSIDE`, `SITE_NETWORK_INSIDE`, `SITE_NETWORK_OUTSIDE`, `SITE_NETWORK_SERVICE`, `SITE_NETWORK_OUTSIDE_WITH_INTERNET_VIP`, `SITE_NETWORK_INSIDE_AND_OUTSIDE_WITH_INTERNET_VIP`, `SITE_NETWORK_IP_FABRIC`<br>[Enum: SITE_NETWORK_INSIDE_AND_OUTSIDE|SITE_NETWORK_INSIDE|SITE_NETWORK_OUTSIDE|SITE_NETWORK_SERVICE|SITE_NETWORK_OUTSIDE_WITH_INTERNET_VIP|SITE_NETWORK_INSIDE_AND_OUTSIDE_WITH_INTERNET_VIP|SITE_NETWORK_IP_FABRIC] Site Network. This defines network types to be used on site All inside and outside networks. All inside and outside networks with internet VIP support. All inside networks. All outside networks. All outside networks with internet VIP support. vK8s service network. - SITE_NETWORK_IP_FABRIC: 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
+
+<a id="advertise-custom-advertise-where-site-site"></a>&#x2022; [`site`](#advertise-custom-advertise-where-site-site) - 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 [Site](#advertise-custom-advertise-where-site-site) below.
+
+#### Advertise Custom Advertise Where Site Site
+
+A [`site`](#advertise-custom-advertise-where-site-site) block (within [`advertise_custom.advertise_where.site`](#advertise-custom-advertise-where-site)) supports the following:
+
+<a id="advertise-custom-advertise-where-site-site-name"></a>&#x2022; [`name`](#advertise-custom-advertise-where-site-site-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="advertise-custom-advertise-where-site-site-namespace"></a>&#x2022; [`namespace`](#advertise-custom-advertise-where-site-site-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="advertise-custom-advertise-where-site-site-tenant"></a>&#x2022; [`tenant`](#advertise-custom-advertise-where-site-site-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
+
+#### Advertise Custom Advertise Where Virtual Network
+
+A [`virtual_network`](#advertise-custom-advertise-where-virtual-network) block (within [`advertise_custom.advertise_where`](#advertise-custom-advertise-where)) supports the following:
+
+<a id="advertise-custom-advertise-where-virtual-network-default-v6-vip"></a>&#x2022; [`default_v6_vip`](#advertise-custom-advertise-where-virtual-network-default-v6-vip) - Optional Block<br>Enable this option
+
+<a id="advertise-custom-advertise-where-virtual-network-default-vip"></a>&#x2022; [`default_vip`](#advertise-custom-advertise-where-virtual-network-default-vip) - Optional Block<br>Enable this option
+
+<a id="advertise-custom-advertise-where-virtual-network-specific-v6-vip"></a>&#x2022; [`specific_v6_vip`](#advertise-custom-advertise-where-virtual-network-specific-v6-vip) - Optional String<br>Specific V6 VIP. Use given IPv6 address as VIP on virtual Network
+
+<a id="advertise-custom-advertise-where-virtual-network-specific-vip"></a>&#x2022; [`specific_vip`](#advertise-custom-advertise-where-virtual-network-specific-vip) - Optional String<br>Specific V4 VIP. Use given IPv4 address as VIP on virtual Network
+
+<a id="advertise-custom-advertise-where-virtual-network-virtual-network"></a>&#x2022; [`virtual_network`](#advertise-custom-advertise-where-virtual-network-virtual-network) - 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 [Virtual Network](#advertise-custom-advertise-where-virtual-network-virtual-network) below.
+
+#### Advertise Custom Advertise Where Virtual Network Virtual Network
+
+A [`virtual_network`](#advertise-custom-advertise-where-virtual-network-virtual-network) block (within [`advertise_custom.advertise_where.virtual_network`](#advertise-custom-advertise-where-virtual-network)) supports the following:
+
+<a id="advertise-custom-advertise-where-virtual-network-virtual-network-name"></a>&#x2022; [`name`](#advertise-custom-advertise-where-virtual-network-virtual-network-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="advertise-custom-advertise-where-virtual-network-virtual-network-namespace"></a>&#x2022; [`namespace`](#advertise-custom-advertise-where-virtual-network-virtual-network-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="advertise-custom-advertise-where-virtual-network-virtual-network-tenant"></a>&#x2022; [`tenant`](#advertise-custom-advertise-where-virtual-network-virtual-network-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
+
+#### Advertise Custom Advertise Where Virtual Site
+
+A [`virtual_site`](#advertise-custom-advertise-where-virtual-site) block (within [`advertise_custom.advertise_where`](#advertise-custom-advertise-where)) supports the following:
+
+<a id="advertise-custom-advertise-where-virtual-site-network"></a>&#x2022; [`network`](#advertise-custom-advertise-where-virtual-site-network) - Optional String  Defaults to `SITE_NETWORK_INSIDE_AND_OUTSIDE`<br>Possible values are `SITE_NETWORK_INSIDE_AND_OUTSIDE`, `SITE_NETWORK_INSIDE`, `SITE_NETWORK_OUTSIDE`, `SITE_NETWORK_SERVICE`, `SITE_NETWORK_OUTSIDE_WITH_INTERNET_VIP`, `SITE_NETWORK_INSIDE_AND_OUTSIDE_WITH_INTERNET_VIP`, `SITE_NETWORK_IP_FABRIC`<br>[Enum: SITE_NETWORK_INSIDE_AND_OUTSIDE|SITE_NETWORK_INSIDE|SITE_NETWORK_OUTSIDE|SITE_NETWORK_SERVICE|SITE_NETWORK_OUTSIDE_WITH_INTERNET_VIP|SITE_NETWORK_INSIDE_AND_OUTSIDE_WITH_INTERNET_VIP|SITE_NETWORK_IP_FABRIC] Site Network. This defines network types to be used on site All inside and outside networks. All inside and outside networks with internet VIP support. All inside networks. All outside networks. All outside networks with internet VIP support. vK8s service network. - SITE_NETWORK_IP_FABRIC: 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
+
+<a id="advertise-custom-advertise-where-virtual-site-virtual-site"></a>&#x2022; [`virtual_site`](#advertise-custom-advertise-where-virtual-site-virtual-site) - 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 [Virtual Site](#advertise-custom-advertise-where-virtual-site-virtual-site) below.
+
+#### Advertise Custom Advertise Where Virtual Site Virtual Site
+
+A [`virtual_site`](#advertise-custom-advertise-where-virtual-site-virtual-site) block (within [`advertise_custom.advertise_where.virtual_site`](#advertise-custom-advertise-where-virtual-site)) supports the following:
+
+<a id="advertise-custom-advertise-where-virtual-site-virtual-site-name"></a>&#x2022; [`name`](#advertise-custom-advertise-where-virtual-site-virtual-site-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="advertise-custom-advertise-where-virtual-site-virtual-site-namespace"></a>&#x2022; [`namespace`](#advertise-custom-advertise-where-virtual-site-virtual-site-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="advertise-custom-advertise-where-virtual-site-virtual-site-tenant"></a>&#x2022; [`tenant`](#advertise-custom-advertise-where-virtual-site-virtual-site-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
+
+#### Advertise Custom Advertise Where Virtual Site With VIP
+
+A [`virtual_site_with_vip`](#advertise-custom-advertise-where-virtual-site-with-vip) block (within [`advertise_custom.advertise_where`](#advertise-custom-advertise-where)) supports the following:
+
+<a id="advertise-custom-advertise-where-virtual-site-with-vip-ip"></a>&#x2022; [`ip`](#advertise-custom-advertise-where-virtual-site-with-vip-ip) - Optional String<br>IP Address. Use given IP address as VIP on the site
+
+<a id="advertise-custom-advertise-where-virtual-site-with-vip-network"></a>&#x2022; [`network`](#advertise-custom-advertise-where-virtual-site-with-vip-network) - Optional String  Defaults to `SITE_NETWORK_SPECIFIED_VIP_OUTSIDE`<br>Possible values are `SITE_NETWORK_SPECIFIED_VIP_OUTSIDE`, `SITE_NETWORK_SPECIFIED_VIP_INSIDE`<br>[Enum: SITE_NETWORK_SPECIFIED_VIP_OUTSIDE|SITE_NETWORK_SPECIFIED_VIP_INSIDE] Site Network. This defines network types to be used on virtual-site with specified VIP All outside networks. All inside networks
+
+<a id="advertise-custom-advertise-where-virtual-site-with-vip-virtual-site"></a>&#x2022; [`virtual_site`](#advertise-custom-advertise-where-virtual-site-with-vip-virtual-site) - 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 [Virtual Site](#advertise-custom-advertise-where-virtual-site-with-vip-virtual-site) below.
+
+#### Advertise Custom Advertise Where Virtual Site With VIP Virtual Site
+
+A [`virtual_site`](#advertise-custom-advertise-where-virtual-site-with-vip-virtual-site) block (within [`advertise_custom.advertise_where.virtual_site_with_vip`](#advertise-custom-advertise-where-virtual-site-with-vip)) supports the following:
+
+<a id="advertise-custom-advertise-where-virtual-site-with-vip-virtual-site-name"></a>&#x2022; [`name`](#advertise-custom-advertise-where-virtual-site-with-vip-virtual-site-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="advertise-custom-advertise-where-virtual-site-with-vip-virtual-site-namespace"></a>&#x2022; [`namespace`](#advertise-custom-advertise-where-virtual-site-with-vip-virtual-site-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="advertise-custom-advertise-where-virtual-site-with-vip-virtual-site-tenant"></a>&#x2022; [`tenant`](#advertise-custom-advertise-where-virtual-site-with-vip-virtual-site-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
+
+#### Advertise Custom Advertise Where Vk8s Service
+
+A [`vk8s_service`](#advertise-custom-advertise-where-vk8s-service) block (within [`advertise_custom.advertise_where`](#advertise-custom-advertise-where)) supports the following:
+
+<a id="advertise-custom-advertise-where-vk8s-service-site"></a>&#x2022; [`site`](#advertise-custom-advertise-where-vk8s-service-site) - 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 [Site](#advertise-custom-advertise-where-vk8s-service-site) below.
+
+<a id="advertise-custom-advertise-where-vk8s-service-virtual-site"></a>&#x2022; [`virtual_site`](#advertise-custom-advertise-where-vk8s-service-virtual-site) - 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 [Virtual Site](#advertise-custom-advertise-where-vk8s-service-virtual-site) below.
+
+#### Advertise Custom Advertise Where Vk8s Service Site
+
+A [`site`](#advertise-custom-advertise-where-vk8s-service-site) block (within [`advertise_custom.advertise_where.vk8s_service`](#advertise-custom-advertise-where-vk8s-service)) supports the following:
+
+<a id="advertise-custom-advertise-where-vk8s-service-site-name"></a>&#x2022; [`name`](#advertise-custom-advertise-where-vk8s-service-site-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="advertise-custom-advertise-where-vk8s-service-site-namespace"></a>&#x2022; [`namespace`](#advertise-custom-advertise-where-vk8s-service-site-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="advertise-custom-advertise-where-vk8s-service-site-tenant"></a>&#x2022; [`tenant`](#advertise-custom-advertise-where-vk8s-service-site-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
+
+#### Advertise Custom Advertise Where Vk8s Service Virtual Site
+
+A [`virtual_site`](#advertise-custom-advertise-where-vk8s-service-virtual-site) block (within [`advertise_custom.advertise_where.vk8s_service`](#advertise-custom-advertise-where-vk8s-service)) supports the following:
+
+<a id="advertise-custom-advertise-where-vk8s-service-virtual-site-name"></a>&#x2022; [`name`](#advertise-custom-advertise-where-vk8s-service-virtual-site-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="advertise-custom-advertise-where-vk8s-service-virtual-site-namespace"></a>&#x2022; [`namespace`](#advertise-custom-advertise-where-vk8s-service-virtual-site-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="advertise-custom-advertise-where-vk8s-service-virtual-site-tenant"></a>&#x2022; [`tenant`](#advertise-custom-advertise-where-vk8s-service-virtual-site-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
+
+#### Advertise On Public
+
+An [`advertise_on_public`](#advertise-on-public) block supports the following:
+
+<a id="advertise-on-public-public-ip"></a>&#x2022; [`public_ip`](#advertise-on-public-public-ip) - 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 [Public IP](#advertise-on-public-public-ip) below.
+
+#### Advertise On Public Public IP
+
+A [`public_ip`](#advertise-on-public-public-ip) block (within [`advertise_on_public`](#advertise-on-public)) supports the following:
+
+<a id="advertise-on-public-public-ip-name"></a>&#x2022; [`name`](#advertise-on-public-public-ip-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="advertise-on-public-public-ip-namespace"></a>&#x2022; [`namespace`](#advertise-on-public-public-ip-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="advertise-on-public-public-ip-tenant"></a>&#x2022; [`tenant`](#advertise-on-public-public-ip-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
+
+#### Origin Pools Weights
+
+An [`origin_pools_weights`](#origin-pools-weights) block supports the following:
+
+<a id="origin-pools-weights-cluster"></a>&#x2022; [`cluster`](#origin-pools-weights-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 [Cluster](#origin-pools-weights-cluster) below.
+
+<a id="origin-pools-weights-endpoint-subsets"></a>&#x2022; [`endpoint_subsets`](#origin-pools-weights-endpoint-subsets) - Optional Block<br>Origin Servers Subsets. Upstream origin pool may be configured to divide its origin servers into subsets based on metadata attached to the origin servers. Routes may then specify the metadata that a endpoint must match in order to be selected by the load balancer For origin servers which are discovered in K8S or Consul cluster, the label of the service is merged with endpoint's labels. In case of Consul, the label is derived from the 'Tag' field. For labels that are common between configured endpoint and discovered service, labels from discovered service takes precedence. List of key-value pairs that will be used as matching metadata. Only those origin servers of upstream origin pool which match this metadata will be selected for load balancing
+
+<a id="origin-pools-weights-pool"></a>&#x2022; [`pool`](#origin-pools-weights-pool) - 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 [Pool](#origin-pools-weights-pool) below.
+
+<a id="origin-pools-weights-priority"></a>&#x2022; [`priority`](#origin-pools-weights-priority) - Optional Number<br>Priority. Priority of this origin pool, valid only with multiple origin pools. Value of 0 will make the pool as lowest priority origin pool Priority of 1 means highest priority and is considered active. When active origin pool is not available, lower priority origin pools are made active as per the increasing priority
+
+<a id="origin-pools-weights-weight"></a>&#x2022; [`weight`](#origin-pools-weights-weight) - Optional Number<br>Weight. Weight of this origin pool, valid only with multiple origin pool. Value of 0 will disable the pool
+
+#### Origin Pools Weights Cluster
+
+A [`cluster`](#origin-pools-weights-cluster) block (within [`origin_pools_weights`](#origin-pools-weights)) supports the following:
+
+<a id="origin-pools-weights-cluster-name"></a>&#x2022; [`name`](#origin-pools-weights-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="origin-pools-weights-cluster-namespace"></a>&#x2022; [`namespace`](#origin-pools-weights-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="origin-pools-weights-cluster-tenant"></a>&#x2022; [`tenant`](#origin-pools-weights-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
+
+#### Origin Pools Weights Pool
+
+A [`pool`](#origin-pools-weights-pool) block (within [`origin_pools_weights`](#origin-pools-weights)) supports the following:
+
+<a id="origin-pools-weights-pool-name"></a>&#x2022; [`name`](#origin-pools-weights-pool-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="origin-pools-weights-pool-namespace"></a>&#x2022; [`namespace`](#origin-pools-weights-pool-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="origin-pools-weights-pool-tenant"></a>&#x2022; [`tenant`](#origin-pools-weights-pool-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
+
+#### Timeouts
+
+A [`timeouts`](#timeouts) block supports the following:
+
+<a id="timeouts-create"></a>&#x2022; [`create`](#timeouts-create) - Optional String (Defaults to `10 minutes`)<br>Used when creating the resource
+
+<a id="timeouts-delete"></a>&#x2022; [`delete`](#timeouts-delete) - Optional String (Defaults to `10 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 `10 minutes`)<br>Used when updating the resource
+
+#### TLS TCP
+
+A [`tls_tcp`](#tls-tcp) block supports the following:
+
+<a id="tls-tcp-tls-cert-params"></a>&#x2022; [`tls_cert_params`](#tls-tcp-tls-cert-params) - Optional Block<br>TLS Parameters. Select TLS Parameters and Certificates<br>See [TLS Cert Params](#tls-tcp-tls-cert-params) below.
+
+<a id="tls-tcp-tls-parameters"></a>&#x2022; [`tls_parameters`](#tls-tcp-tls-parameters) - Optional Block<br>Inline TLS Parameters. Inline TLS parameters<br>See [TLS Parameters](#tls-tcp-tls-parameters) below.
+
+#### TLS TCP TLS Cert Params
+
+A [`tls_cert_params`](#tls-tcp-tls-cert-params) block (within [`tls_tcp`](#tls-tcp)) supports the following:
+
+<a id="tls-tcp-tls-cert-params-certificates"></a>&#x2022; [`certificates`](#tls-tcp-tls-cert-params-certificates) - Optional Block<br>Certificates. Select one or more certificates with any domain names<br>See [Certificates](#tls-tcp-tls-cert-params-certificates) below.
+
+<a id="tls-tcp-tls-cert-params-no-mtls"></a>&#x2022; [`no_mtls`](#tls-tcp-tls-cert-params-no-mtls) - Optional Block<br>Enable this option
+
+<a id="tls-tcp-tls-cert-params-tls-config"></a>&#x2022; [`tls_config`](#tls-tcp-tls-cert-params-tls-config) - Optional Block<br>TLS Config. This defines various options to configure TLS configuration parameters<br>See [TLS Config](#tls-tcp-tls-cert-params-tls-config) below.
+
+<a id="tls-tcp-tls-cert-params-use-mtls"></a>&#x2022; [`use_mtls`](#tls-tcp-tls-cert-params-use-mtls) - Optional Block<br>Clients TLS validation context. Validation context for downstream client TLS connections<br>See [Use mTLS](#tls-tcp-tls-cert-params-use-mtls) below.
+
+#### TLS TCP TLS Cert Params Certificates
+
+A [`certificates`](#tls-tcp-tls-cert-params-certificates) block (within [`tls_tcp.tls_cert_params`](#tls-tcp-tls-cert-params)) supports the following:
+
+<a id="tls-tcp-tls-cert-params-certificates-name"></a>&#x2022; [`name`](#tls-tcp-tls-cert-params-certificates-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="tls-tcp-tls-cert-params-certificates-namespace"></a>&#x2022; [`namespace`](#tls-tcp-tls-cert-params-certificates-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="tls-tcp-tls-cert-params-certificates-tenant"></a>&#x2022; [`tenant`](#tls-tcp-tls-cert-params-certificates-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
+
+#### TLS TCP TLS Cert Params TLS Config
+
+A [`tls_config`](#tls-tcp-tls-cert-params-tls-config) block (within [`tls_tcp.tls_cert_params`](#tls-tcp-tls-cert-params)) supports the following:
+
+<a id="tls-tcp-tls-cert-params-tls-config-custom-security"></a>&#x2022; [`custom_security`](#tls-tcp-tls-cert-params-tls-config-custom-security) - Optional Block<br>Custom Ciphers. This defines TLS protocol config including min/max versions and allowed ciphers<br>See [Custom Security](#tls-tcp-tls-cert-params-tls-config-custom-security) below.
+
+<a id="tls-tcp-tls-cert-params-tls-config-default-security"></a>&#x2022; [`default_security`](#tls-tcp-tls-cert-params-tls-config-default-security) - Optional Block<br>Enable this option
+
+<a id="tls-tcp-tls-cert-params-tls-config-low-security"></a>&#x2022; [`low_security`](#tls-tcp-tls-cert-params-tls-config-low-security) - Optional Block<br>Enable this option
+
+<a id="tls-tcp-tls-cert-params-tls-config-medium-security"></a>&#x2022; [`medium_security`](#tls-tcp-tls-cert-params-tls-config-medium-security) - Optional Block<br>Enable this option
+
+#### TLS TCP TLS Cert Params TLS Config Custom Security
+
+A [`custom_security`](#tls-tcp-tls-cert-params-tls-config-custom-security) block (within [`tls_tcp.tls_cert_params.tls_config`](#tls-tcp-tls-cert-params-tls-config)) supports the following:
+
+<a id="tls-tcp-tls-cert-params-tls-config-custom-security-cipher-suites"></a>&#x2022; [`cipher_suites`](#tls-tcp-tls-cert-params-tls-config-custom-security-cipher-suites) - Optional List<br>Cipher Suites. The TLS listener will only support the specified cipher list
+
+<a id="tls-tcp-tls-cert-params-tls-config-custom-security-max-version"></a>&#x2022; [`max_version`](#tls-tcp-tls-cert-params-tls-config-custom-security-max-version) - Optional String  Defaults to `TLS_AUTO`<br>Possible values are `TLS_AUTO`, `TLSv1_0`, `TLSv1_1`, `TLSv1_2`, `TLSv1_3`<br>[Enum: TLS_AUTO|TLSv1_0|TLSv1_1|TLSv1_2|TLSv1_3] TLS Protocol. TlsProtocol is enumeration of supported TLS versions F5 Distributed Cloud will choose the optimal TLS version
+
+<a id="tls-tcp-tls-cert-params-tls-config-custom-security-min-version"></a>&#x2022; [`min_version`](#tls-tcp-tls-cert-params-tls-config-custom-security-min-version) - Optional String  Defaults to `TLS_AUTO`<br>Possible values are `TLS_AUTO`, `TLSv1_0`, `TLSv1_1`, `TLSv1_2`, `TLSv1_3`<br>[Enum: TLS_AUTO|TLSv1_0|TLSv1_1|TLSv1_2|TLSv1_3] TLS Protocol. TlsProtocol is enumeration of supported TLS versions F5 Distributed Cloud will choose the optimal TLS version
+
+#### TLS TCP TLS Cert Params Use mTLS
+
+An [`use_mtls`](#tls-tcp-tls-cert-params-use-mtls) block (within [`tls_tcp.tls_cert_params`](#tls-tcp-tls-cert-params)) supports the following:
+
+<a id="tls-tcp-tls-cert-params-use-mtls-client-certificate-optional"></a>&#x2022; [`client_certificate_optional`](#tls-tcp-tls-cert-params-use-mtls-client-certificate-optional) - Optional Bool<br>Client Certificate Optional. Client certificate is optional. If the client has provided a certificate, the load balancer will verify it. If certification verification fails, the connection will be terminated. If the client does not provide a certificate, the connection will be accepted
+
+<a id="tls-tcp-tls-cert-params-use-mtls-crl"></a>&#x2022; [`crl`](#tls-tcp-tls-cert-params-use-mtls-crl) - 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 [CRL](#tls-tcp-tls-cert-params-use-mtls-crl) below.
+
+<a id="tls-tcp-tls-cert-params-use-mtls-no-crl"></a>&#x2022; [`no_crl`](#tls-tcp-tls-cert-params-use-mtls-no-crl) - Optional Block<br>Enable this option
+
+<a id="tls-tcp-tls-cert-params-use-mtls-trusted-ca"></a>&#x2022; [`trusted_ca`](#tls-tcp-tls-cert-params-use-mtls-trusted-ca) - 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 [Trusted CA](#tls-tcp-tls-cert-params-use-mtls-trusted-ca) below.
+
+<a id="tls-tcp-tls-cert-params-use-mtls-trusted-ca-url"></a>&#x2022; [`trusted_ca_url`](#tls-tcp-tls-cert-params-use-mtls-trusted-ca-url) - Optional String<br>Inline Root CA Certificate (legacy). Upload a Root CA Certificate specifically for this Load Balancer
+
+<a id="tls-tcp-tls-cert-params-use-mtls-xfcc-disabled"></a>&#x2022; [`xfcc_disabled`](#tls-tcp-tls-cert-params-use-mtls-xfcc-disabled) - Optional Block<br>Enable this option
+
+<a id="tls-tcp-tls-cert-params-use-mtls-xfcc-options"></a>&#x2022; [`xfcc_options`](#tls-tcp-tls-cert-params-use-mtls-xfcc-options) - Optional Block<br>XFCC Header Elements. X-Forwarded-Client-Cert header elements to be added to requests<br>See [Xfcc Options](#tls-tcp-tls-cert-params-use-mtls-xfcc-options) below.
+
+#### TLS TCP TLS Cert Params Use mTLS CRL
+
+A [`crl`](#tls-tcp-tls-cert-params-use-mtls-crl) block (within [`tls_tcp.tls_cert_params.use_mtls`](#tls-tcp-tls-cert-params-use-mtls)) supports the following:
+
+<a id="tls-tcp-tls-cert-params-use-mtls-crl-name"></a>&#x2022; [`name`](#tls-tcp-tls-cert-params-use-mtls-crl-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="tls-tcp-tls-cert-params-use-mtls-crl-namespace"></a>&#x2022; [`namespace`](#tls-tcp-tls-cert-params-use-mtls-crl-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="tls-tcp-tls-cert-params-use-mtls-crl-tenant"></a>&#x2022; [`tenant`](#tls-tcp-tls-cert-params-use-mtls-crl-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
+
+#### TLS TCP TLS Cert Params Use mTLS Trusted CA
+
+A [`trusted_ca`](#tls-tcp-tls-cert-params-use-mtls-trusted-ca) block (within [`tls_tcp.tls_cert_params.use_mtls`](#tls-tcp-tls-cert-params-use-mtls)) supports the following:
+
+<a id="tls-tcp-tls-cert-params-use-mtls-trusted-ca-name"></a>&#x2022; [`name`](#tls-tcp-tls-cert-params-use-mtls-trusted-ca-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="tls-tcp-tls-cert-params-use-mtls-trusted-ca-namespace"></a>&#x2022; [`namespace`](#tls-tcp-tls-cert-params-use-mtls-trusted-ca-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="tls-tcp-tls-cert-params-use-mtls-trusted-ca-tenant"></a>&#x2022; [`tenant`](#tls-tcp-tls-cert-params-use-mtls-trusted-ca-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
+
+#### TLS TCP TLS Cert Params Use mTLS Xfcc Options
+
+A [`xfcc_options`](#tls-tcp-tls-cert-params-use-mtls-xfcc-options) block (within [`tls_tcp.tls_cert_params.use_mtls`](#tls-tcp-tls-cert-params-use-mtls)) supports the following:
+
+<a id="tls-tcp-tls-cert-params-use-mtls-xfcc-options-xfcc-header-elements"></a>&#x2022; [`xfcc_header_elements`](#tls-tcp-tls-cert-params-use-mtls-xfcc-options-xfcc-header-elements) - Optional List  Defaults to `XFCC_NONE`<br>Possible values are `XFCC_NONE`, `XFCC_CERT`, `XFCC_CHAIN`, `XFCC_SUBJECT`, `XFCC_URI`, `XFCC_DNS`<br>[Enum: XFCC_NONE|XFCC_CERT|XFCC_CHAIN|XFCC_SUBJECT|XFCC_URI|XFCC_DNS] XFCC Header Elements. X-Forwarded-Client-Cert header elements to be added to requests
+
+#### TLS TCP TLS Parameters
+
+A [`tls_parameters`](#tls-tcp-tls-parameters) block (within [`tls_tcp`](#tls-tcp)) supports the following:
+
+<a id="tls-tcp-tls-parameters-no-mtls"></a>&#x2022; [`no_mtls`](#tls-tcp-tls-parameters-no-mtls) - Optional Block<br>Enable this option
+
+<a id="tls-tcp-tls-parameters-tls-certificates"></a>&#x2022; [`tls_certificates`](#tls-tcp-tls-parameters-tls-certificates) - Optional Block<br>TLS Certificates. Users can add one or more certificates that share the same set of domains. for example, domain.com and \*.domain.com - but use different signature algorithms<br>See [TLS Certificates](#tls-tcp-tls-parameters-tls-certificates) below.
+
+<a id="tls-tcp-tls-parameters-tls-config"></a>&#x2022; [`tls_config`](#tls-tcp-tls-parameters-tls-config) - Optional Block<br>TLS Config. This defines various options to configure TLS configuration parameters<br>See [TLS Config](#tls-tcp-tls-parameters-tls-config) below.
+
+<a id="tls-tcp-tls-parameters-use-mtls"></a>&#x2022; [`use_mtls`](#tls-tcp-tls-parameters-use-mtls) - Optional Block<br>Clients TLS validation context. Validation context for downstream client TLS connections<br>See [Use mTLS](#tls-tcp-tls-parameters-use-mtls) below.
+
+#### TLS TCP TLS Parameters TLS Certificates
+
+A [`tls_certificates`](#tls-tcp-tls-parameters-tls-certificates) block (within [`tls_tcp.tls_parameters`](#tls-tcp-tls-parameters)) supports the following:
+
+<a id="tls-tcp-tls-parameters-tls-certificates-certificate-url"></a>&#x2022; [`certificate_url`](#tls-tcp-tls-parameters-tls-certificates-certificate-url) - Optional String<br>Certificate. TLS certificate. Certificate or certificate chain in PEM format including the PEM headers
+
+<a id="tls-tcp-tls-parameters-tls-certificates-custom-hash-algorithms"></a>&#x2022; [`custom_hash_algorithms`](#tls-tcp-tls-parameters-tls-certificates-custom-hash-algorithms) - Optional Block<br>Hash Algorithms. Specifies the hash algorithms to be used<br>See [Custom Hash Algorithms](#tls-tcp-tls-parameters-tls-certificates-custom-hash-algorithms) below.
+
+<a id="tls-tcp-tls-parameters-tls-certificates-description-spec"></a>&#x2022; [`description_spec`](#tls-tcp-tls-parameters-tls-certificates-description-spec) - Optional String<br>Description. Description for the certificate
+
+<a id="tls-tcp-tls-parameters-tls-certificates-disable-ocsp-stapling"></a>&#x2022; [`disable_ocsp_stapling`](#tls-tcp-tls-parameters-tls-certificates-disable-ocsp-stapling) - Optional Block<br>Enable this option
+
+<a id="tls-tcp-tls-parameters-tls-certificates-private-key"></a>&#x2022; [`private_key`](#tls-tcp-tls-parameters-tls-certificates-private-key) - Optional Block<br>Secret. SecretType is used in an object to indicate a sensitive/confidential field<br>See [Private Key](#tls-tcp-tls-parameters-tls-certificates-private-key) below.
+
+<a id="tls-tcp-tls-parameters-tls-certificates-use-system-defaults"></a>&#x2022; [`use_system_defaults`](#tls-tcp-tls-parameters-tls-certificates-use-system-defaults) - Optional Block<br>Enable this option
+
+#### TLS TCP TLS Parameters TLS Certificates Custom Hash Algorithms
+
+A [`custom_hash_algorithms`](#tls-tcp-tls-parameters-tls-certificates-custom-hash-algorithms) block (within [`tls_tcp.tls_parameters.tls_certificates`](#tls-tcp-tls-parameters-tls-certificates)) supports the following:
+
+<a id="tls-tcp-tls-parameters-tls-certificates-custom-hash-algorithms-hash-algorithms"></a>&#x2022; [`hash_algorithms`](#tls-tcp-tls-parameters-tls-certificates-custom-hash-algorithms-hash-algorithms) - Optional List  Defaults to `INVALID_HASH_ALGORITHM`<br>Possible values are `INVALID_HASH_ALGORITHM`, `SHA256`, `SHA1`<br>[Enum: INVALID_HASH_ALGORITHM|SHA256|SHA1] Hash Algorithms. Ordered list of hash algorithms to be used
+
+#### TLS TCP TLS Parameters TLS Certificates Private Key
+
+A [`private_key`](#tls-tcp-tls-parameters-tls-certificates-private-key) block (within [`tls_tcp.tls_parameters.tls_certificates`](#tls-tcp-tls-parameters-tls-certificates)) supports the following:
+
+<a id="tls-tcp-tls-parameters-tls-certificates-private-key-blindfold-secret-info"></a>&#x2022; [`blindfold_secret_info`](#tls-tcp-tls-parameters-tls-certificates-private-key-blindfold-secret-info) - Optional Block<br>Blindfold Secret. BlindfoldSecretInfoType specifies information about the Secret managed by F5XC Secret Management<br>See [Blindfold Secret Info](#tls-tcp-tls-parameters-tls-certificates-private-key-blindfold-secret-info) below.
+
+<a id="tls-tcp-tls-parameters-tls-certificates-private-key-clear-secret-info"></a>&#x2022; [`clear_secret_info`](#tls-tcp-tls-parameters-tls-certificates-private-key-clear-secret-info) - Optional Block<br>In-Clear Secret. ClearSecretInfoType specifies information about the Secret that is not encrypted<br>See [Clear Secret Info](#tls-tcp-tls-parameters-tls-certificates-private-key-clear-secret-info) below.
+
+#### TLS TCP TLS Parameters TLS Certificates Private Key Blindfold Secret Info
+
+A [`blindfold_secret_info`](#tls-tcp-tls-parameters-tls-certificates-private-key-blindfold-secret-info) block (within [`tls_tcp.tls_parameters.tls_certificates.private_key`](#tls-tcp-tls-parameters-tls-certificates-private-key)) supports the following:
+
+<a id="tls-tcp-tls-parameters-tls-certificates-private-key-blindfold-secret-info-decryption-provider"></a>&#x2022; [`decryption_provider`](#tls-tcp-tls-parameters-tls-certificates-private-key-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="tls-tcp-tls-parameters-tls-certificates-private-key-blindfold-secret-info-location"></a>&#x2022; [`location`](#tls-tcp-tls-parameters-tls-certificates-private-key-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="tls-tcp-tls-parameters-tls-certificates-private-key-blindfold-secret-info-store-provider"></a>&#x2022; [`store_provider`](#tls-tcp-tls-parameters-tls-certificates-private-key-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:///
+
+#### TLS TCP TLS Parameters TLS Certificates Private Key Clear Secret Info
+
+A [`clear_secret_info`](#tls-tcp-tls-parameters-tls-certificates-private-key-clear-secret-info) block (within [`tls_tcp.tls_parameters.tls_certificates.private_key`](#tls-tcp-tls-parameters-tls-certificates-private-key)) supports the following:
+
+<a id="tls-tcp-tls-parameters-tls-certificates-private-key-clear-secret-info-provider-ref"></a>&#x2022; [`provider_ref`](#tls-tcp-tls-parameters-tls-certificates-private-key-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="tls-tcp-tls-parameters-tls-certificates-private-key-clear-secret-info-url"></a>&#x2022; [`url`](#tls-tcp-tls-parameters-tls-certificates-private-key-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
+
+#### TLS TCP TLS Parameters TLS Config
+
+A [`tls_config`](#tls-tcp-tls-parameters-tls-config) block (within [`tls_tcp.tls_parameters`](#tls-tcp-tls-parameters)) supports the following:
+
+<a id="tls-tcp-tls-parameters-tls-config-custom-security"></a>&#x2022; [`custom_security`](#tls-tcp-tls-parameters-tls-config-custom-security) - Optional Block<br>Custom Ciphers. This defines TLS protocol config including min/max versions and allowed ciphers<br>See [Custom Security](#tls-tcp-tls-parameters-tls-config-custom-security) below.
+
+<a id="tls-tcp-tls-parameters-tls-config-default-security"></a>&#x2022; [`default_security`](#tls-tcp-tls-parameters-tls-config-default-security) - Optional Block<br>Enable this option
+
+<a id="tls-tcp-tls-parameters-tls-config-low-security"></a>&#x2022; [`low_security`](#tls-tcp-tls-parameters-tls-config-low-security) - Optional Block<br>Enable this option
+
+<a id="tls-tcp-tls-parameters-tls-config-medium-security"></a>&#x2022; [`medium_security`](#tls-tcp-tls-parameters-tls-config-medium-security) - Optional Block<br>Enable this option
+
+#### TLS TCP TLS Parameters TLS Config Custom Security
+
+A [`custom_security`](#tls-tcp-tls-parameters-tls-config-custom-security) block (within [`tls_tcp.tls_parameters.tls_config`](#tls-tcp-tls-parameters-tls-config)) supports the following:
+
+<a id="tls-tcp-tls-parameters-tls-config-custom-security-cipher-suites"></a>&#x2022; [`cipher_suites`](#tls-tcp-tls-parameters-tls-config-custom-security-cipher-suites) - Optional List<br>Cipher Suites. The TLS listener will only support the specified cipher list
+
+<a id="tls-tcp-tls-parameters-tls-config-custom-security-max-version"></a>&#x2022; [`max_version`](#tls-tcp-tls-parameters-tls-config-custom-security-max-version) - Optional String  Defaults to `TLS_AUTO`<br>Possible values are `TLS_AUTO`, `TLSv1_0`, `TLSv1_1`, `TLSv1_2`, `TLSv1_3`<br>[Enum: TLS_AUTO|TLSv1_0|TLSv1_1|TLSv1_2|TLSv1_3] TLS Protocol. TlsProtocol is enumeration of supported TLS versions F5 Distributed Cloud will choose the optimal TLS version
+
+<a id="tls-tcp-tls-parameters-tls-config-custom-security-min-version"></a>&#x2022; [`min_version`](#tls-tcp-tls-parameters-tls-config-custom-security-min-version) - Optional String  Defaults to `TLS_AUTO`<br>Possible values are `TLS_AUTO`, `TLSv1_0`, `TLSv1_1`, `TLSv1_2`, `TLSv1_3`<br>[Enum: TLS_AUTO|TLSv1_0|TLSv1_1|TLSv1_2|TLSv1_3] TLS Protocol. TlsProtocol is enumeration of supported TLS versions F5 Distributed Cloud will choose the optimal TLS version
+
+#### TLS TCP TLS Parameters Use mTLS
+
+An [`use_mtls`](#tls-tcp-tls-parameters-use-mtls) block (within [`tls_tcp.tls_parameters`](#tls-tcp-tls-parameters)) supports the following:
+
+<a id="tls-tcp-tls-parameters-use-mtls-client-certificate-optional"></a>&#x2022; [`client_certificate_optional`](#tls-tcp-tls-parameters-use-mtls-client-certificate-optional) - Optional Bool<br>Client Certificate Optional. Client certificate is optional. If the client has provided a certificate, the load balancer will verify it. If certification verification fails, the connection will be terminated. If the client does not provide a certificate, the connection will be accepted
+
+<a id="tls-tcp-tls-parameters-use-mtls-crl"></a>&#x2022; [`crl`](#tls-tcp-tls-parameters-use-mtls-crl) - 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 [CRL](#tls-tcp-tls-parameters-use-mtls-crl) below.
+
+<a id="tls-tcp-tls-parameters-use-mtls-no-crl"></a>&#x2022; [`no_crl`](#tls-tcp-tls-parameters-use-mtls-no-crl) - Optional Block<br>Enable this option
+
+<a id="tls-tcp-tls-parameters-use-mtls-trusted-ca"></a>&#x2022; [`trusted_ca`](#tls-tcp-tls-parameters-use-mtls-trusted-ca) - 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 [Trusted CA](#tls-tcp-tls-parameters-use-mtls-trusted-ca) below.
+
+<a id="tls-tcp-tls-parameters-use-mtls-trusted-ca-url"></a>&#x2022; [`trusted_ca_url`](#tls-tcp-tls-parameters-use-mtls-trusted-ca-url) - Optional String<br>Inline Root CA Certificate (legacy). Upload a Root CA Certificate specifically for this Load Balancer
+
+<a id="tls-tcp-tls-parameters-use-mtls-xfcc-disabled"></a>&#x2022; [`xfcc_disabled`](#tls-tcp-tls-parameters-use-mtls-xfcc-disabled) - Optional Block<br>Enable this option
+
+<a id="tls-tcp-tls-parameters-use-mtls-xfcc-options"></a>&#x2022; [`xfcc_options`](#tls-tcp-tls-parameters-use-mtls-xfcc-options) - Optional Block<br>XFCC Header Elements. X-Forwarded-Client-Cert header elements to be added to requests<br>See [Xfcc Options](#tls-tcp-tls-parameters-use-mtls-xfcc-options) below.
+
+#### TLS TCP TLS Parameters Use mTLS CRL
+
+A [`crl`](#tls-tcp-tls-parameters-use-mtls-crl) block (within [`tls_tcp.tls_parameters.use_mtls`](#tls-tcp-tls-parameters-use-mtls)) supports the following:
+
+<a id="tls-tcp-tls-parameters-use-mtls-crl-name"></a>&#x2022; [`name`](#tls-tcp-tls-parameters-use-mtls-crl-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="tls-tcp-tls-parameters-use-mtls-crl-namespace"></a>&#x2022; [`namespace`](#tls-tcp-tls-parameters-use-mtls-crl-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="tls-tcp-tls-parameters-use-mtls-crl-tenant"></a>&#x2022; [`tenant`](#tls-tcp-tls-parameters-use-mtls-crl-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
+
+#### TLS TCP TLS Parameters Use mTLS Trusted CA
+
+A [`trusted_ca`](#tls-tcp-tls-parameters-use-mtls-trusted-ca) block (within [`tls_tcp.tls_parameters.use_mtls`](#tls-tcp-tls-parameters-use-mtls)) supports the following:
+
+<a id="tls-tcp-tls-parameters-use-mtls-trusted-ca-name"></a>&#x2022; [`name`](#tls-tcp-tls-parameters-use-mtls-trusted-ca-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="tls-tcp-tls-parameters-use-mtls-trusted-ca-namespace"></a>&#x2022; [`namespace`](#tls-tcp-tls-parameters-use-mtls-trusted-ca-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="tls-tcp-tls-parameters-use-mtls-trusted-ca-tenant"></a>&#x2022; [`tenant`](#tls-tcp-tls-parameters-use-mtls-trusted-ca-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
+
+#### TLS TCP TLS Parameters Use mTLS Xfcc Options
+
+A [`xfcc_options`](#tls-tcp-tls-parameters-use-mtls-xfcc-options) block (within [`tls_tcp.tls_parameters.use_mtls`](#tls-tcp-tls-parameters-use-mtls)) supports the following:
+
+<a id="tls-tcp-tls-parameters-use-mtls-xfcc-options-xfcc-header-elements"></a>&#x2022; [`xfcc_header_elements`](#tls-tcp-tls-parameters-use-mtls-xfcc-options-xfcc-header-elements) - Optional List  Defaults to `XFCC_NONE`<br>Possible values are `XFCC_NONE`, `XFCC_CERT`, `XFCC_CHAIN`, `XFCC_SUBJECT`, `XFCC_URI`, `XFCC_DNS`<br>[Enum: XFCC_NONE|XFCC_CERT|XFCC_CHAIN|XFCC_SUBJECT|XFCC_URI|XFCC_DNS] XFCC Header Elements. X-Forwarded-Client-Cert header elements to be added to requests
+
+#### TLS TCP Auto Cert
+
+A [`tls_tcp_auto_cert`](#tls-tcp-auto-cert) block supports the following:
+
+<a id="tls-tcp-auto-cert-no-mtls"></a>&#x2022; [`no_mtls`](#tls-tcp-auto-cert-no-mtls) - Optional Block<br>Enable this option
+
+<a id="tls-tcp-auto-cert-tls-config"></a>&#x2022; [`tls_config`](#tls-tcp-auto-cert-tls-config) - Optional Block<br>TLS Config. This defines various options to configure TLS configuration parameters<br>See [TLS Config](#tls-tcp-auto-cert-tls-config) below.
+
+<a id="tls-tcp-auto-cert-use-mtls"></a>&#x2022; [`use_mtls`](#tls-tcp-auto-cert-use-mtls) - Optional Block<br>Clients TLS validation context. Validation context for downstream client TLS connections<br>See [Use mTLS](#tls-tcp-auto-cert-use-mtls) below.
+
+#### TLS TCP Auto Cert TLS Config
+
+A [`tls_config`](#tls-tcp-auto-cert-tls-config) block (within [`tls_tcp_auto_cert`](#tls-tcp-auto-cert)) supports the following:
+
+<a id="tls-tcp-auto-cert-tls-config-custom-security"></a>&#x2022; [`custom_security`](#tls-tcp-auto-cert-tls-config-custom-security) - Optional Block<br>Custom Ciphers. This defines TLS protocol config including min/max versions and allowed ciphers<br>See [Custom Security](#tls-tcp-auto-cert-tls-config-custom-security) below.
+
+<a id="tls-tcp-auto-cert-tls-config-default-security"></a>&#x2022; [`default_security`](#tls-tcp-auto-cert-tls-config-default-security) - Optional Block<br>Enable this option
+
+<a id="tls-tcp-auto-cert-tls-config-low-security"></a>&#x2022; [`low_security`](#tls-tcp-auto-cert-tls-config-low-security) - Optional Block<br>Enable this option
+
+<a id="tls-tcp-auto-cert-tls-config-medium-security"></a>&#x2022; [`medium_security`](#tls-tcp-auto-cert-tls-config-medium-security) - Optional Block<br>Enable this option
+
+#### TLS TCP Auto Cert TLS Config Custom Security
+
+A [`custom_security`](#tls-tcp-auto-cert-tls-config-custom-security) block (within [`tls_tcp_auto_cert.tls_config`](#tls-tcp-auto-cert-tls-config)) supports the following:
+
+<a id="tls-tcp-auto-cert-tls-config-custom-security-cipher-suites"></a>&#x2022; [`cipher_suites`](#tls-tcp-auto-cert-tls-config-custom-security-cipher-suites) - Optional List<br>Cipher Suites. The TLS listener will only support the specified cipher list
+
+<a id="tls-tcp-auto-cert-tls-config-custom-security-max-version"></a>&#x2022; [`max_version`](#tls-tcp-auto-cert-tls-config-custom-security-max-version) - Optional String  Defaults to `TLS_AUTO`<br>Possible values are `TLS_AUTO`, `TLSv1_0`, `TLSv1_1`, `TLSv1_2`, `TLSv1_3`<br>[Enum: TLS_AUTO|TLSv1_0|TLSv1_1|TLSv1_2|TLSv1_3] TLS Protocol. TlsProtocol is enumeration of supported TLS versions F5 Distributed Cloud will choose the optimal TLS version
+
+<a id="tls-tcp-auto-cert-tls-config-custom-security-min-version"></a>&#x2022; [`min_version`](#tls-tcp-auto-cert-tls-config-custom-security-min-version) - Optional String  Defaults to `TLS_AUTO`<br>Possible values are `TLS_AUTO`, `TLSv1_0`, `TLSv1_1`, `TLSv1_2`, `TLSv1_3`<br>[Enum: TLS_AUTO|TLSv1_0|TLSv1_1|TLSv1_2|TLSv1_3] TLS Protocol. TlsProtocol is enumeration of supported TLS versions F5 Distributed Cloud will choose the optimal TLS version
+
+#### TLS TCP Auto Cert Use mTLS
+
+An [`use_mtls`](#tls-tcp-auto-cert-use-mtls) block (within [`tls_tcp_auto_cert`](#tls-tcp-auto-cert)) supports the following:
+
+<a id="tls-tcp-auto-cert-use-mtls-client-certificate-optional"></a>&#x2022; [`client_certificate_optional`](#tls-tcp-auto-cert-use-mtls-client-certificate-optional) - Optional Bool<br>Client Certificate Optional. Client certificate is optional. If the client has provided a certificate, the load balancer will verify it. If certification verification fails, the connection will be terminated. If the client does not provide a certificate, the connection will be accepted
+
+<a id="tls-tcp-auto-cert-use-mtls-crl"></a>&#x2022; [`crl`](#tls-tcp-auto-cert-use-mtls-crl) - 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 [CRL](#tls-tcp-auto-cert-use-mtls-crl) below.
+
+<a id="tls-tcp-auto-cert-use-mtls-no-crl"></a>&#x2022; [`no_crl`](#tls-tcp-auto-cert-use-mtls-no-crl) - Optional Block<br>Enable this option
+
+<a id="tls-tcp-auto-cert-use-mtls-trusted-ca"></a>&#x2022; [`trusted_ca`](#tls-tcp-auto-cert-use-mtls-trusted-ca) - 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 [Trusted CA](#tls-tcp-auto-cert-use-mtls-trusted-ca) below.
+
+<a id="tls-tcp-auto-cert-use-mtls-trusted-ca-url"></a>&#x2022; [`trusted_ca_url`](#tls-tcp-auto-cert-use-mtls-trusted-ca-url) - Optional String<br>Inline Root CA Certificate (legacy). Upload a Root CA Certificate specifically for this Load Balancer
+
+<a id="tls-tcp-auto-cert-use-mtls-xfcc-disabled"></a>&#x2022; [`xfcc_disabled`](#tls-tcp-auto-cert-use-mtls-xfcc-disabled) - Optional Block<br>Enable this option
+
+<a id="tls-tcp-auto-cert-use-mtls-xfcc-options"></a>&#x2022; [`xfcc_options`](#tls-tcp-auto-cert-use-mtls-xfcc-options) - Optional Block<br>XFCC Header Elements. X-Forwarded-Client-Cert header elements to be added to requests<br>See [Xfcc Options](#tls-tcp-auto-cert-use-mtls-xfcc-options) below.
+
+#### TLS TCP Auto Cert Use mTLS CRL
+
+A [`crl`](#tls-tcp-auto-cert-use-mtls-crl) block (within [`tls_tcp_auto_cert.use_mtls`](#tls-tcp-auto-cert-use-mtls)) supports the following:
+
+<a id="tls-tcp-auto-cert-use-mtls-crl-name"></a>&#x2022; [`name`](#tls-tcp-auto-cert-use-mtls-crl-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="tls-tcp-auto-cert-use-mtls-crl-namespace"></a>&#x2022; [`namespace`](#tls-tcp-auto-cert-use-mtls-crl-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="tls-tcp-auto-cert-use-mtls-crl-tenant"></a>&#x2022; [`tenant`](#tls-tcp-auto-cert-use-mtls-crl-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
+
+#### TLS TCP Auto Cert Use mTLS Trusted CA
+
+A [`trusted_ca`](#tls-tcp-auto-cert-use-mtls-trusted-ca) block (within [`tls_tcp_auto_cert.use_mtls`](#tls-tcp-auto-cert-use-mtls)) supports the following:
+
+<a id="tls-tcp-auto-cert-use-mtls-trusted-ca-name"></a>&#x2022; [`name`](#tls-tcp-auto-cert-use-mtls-trusted-ca-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="tls-tcp-auto-cert-use-mtls-trusted-ca-namespace"></a>&#x2022; [`namespace`](#tls-tcp-auto-cert-use-mtls-trusted-ca-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="tls-tcp-auto-cert-use-mtls-trusted-ca-tenant"></a>&#x2022; [`tenant`](#tls-tcp-auto-cert-use-mtls-trusted-ca-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
+
+#### TLS TCP Auto Cert Use mTLS Xfcc Options
+
+A [`xfcc_options`](#tls-tcp-auto-cert-use-mtls-xfcc-options) block (within [`tls_tcp_auto_cert.use_mtls`](#tls-tcp-auto-cert-use-mtls)) supports the following:
+
+<a id="tls-tcp-auto-cert-use-mtls-xfcc-options-xfcc-header-elements"></a>&#x2022; [`xfcc_header_elements`](#tls-tcp-auto-cert-use-mtls-xfcc-options-xfcc-header-elements) - Optional List  Defaults to `XFCC_NONE`<br>Possible values are `XFCC_NONE`, `XFCC_CERT`, `XFCC_CHAIN`, `XFCC_SUBJECT`, `XFCC_URI`, `XFCC_DNS`<br>[Enum: XFCC_NONE|XFCC_CERT|XFCC_CHAIN|XFCC_SUBJECT|XFCC_URI|XFCC_DNS] XFCC Header Elements. X-Forwarded-Client-Cert header elements to be added to requests
+
+## Import
+
+Import is supported using the following syntax:
+
+```shell
+# Import using namespace/name format
+terraform import f5xc_tcp_loadbalancer.example system/example
+```