@robinmordasiewicz/f5xc-terraform-mcp 2.3.0 → 2.4.3

package/dist/docs/resources/origin_pool.md

@@ -0,0 +1,801 @@
+---
+page_title: "f5xc_origin_pool Resource - terraform-provider-f5xc"
+subcategory: "Load Balancing"
+description: |-
+  [Category: Load Balancing] [Namespace: required] [DependsOn: namespace, healthcheck] Manages a Origin Pool resource in F5 Distributed Cloud for defining backend server pools for load balancer targets.
+---
+
+# f5xc_origin_pool (Resource)
+
+[Category: Load Balancing] [Namespace: required] [DependsOn: namespace, healthcheck] Manages a Origin Pool resource in F5 Distributed Cloud for defining backend server pools for load balancer targets.
+
+~> **Note** Please refer to [Origin Pool API docs](https://docs.cloud.f5.com/docs-v2/api/views-origin-pool) to learn more.
+
+## Example Usage
+
+```terraform
+# Origin Pool Resource Example
+# [Category: Load Balancing] [Namespace: required] [DependsOn: namespace, healthcheck] Manages a Origin Pool resource in F5 Distributed Cloud for defining backend server pools for load balancer targets.
+
+# Basic Origin Pool configuration
+resource "f5xc_origin_pool" "example" {
+  name      = "example-origin-pool"
+  namespace = "staging"
+
+  labels = {
+    environment = "production"
+    managed_by  = "terraform"
+  }
+
+  annotations = {
+    "owner" = "platform-team"
+  }
+
+  // Origin servers configuration
+  origin_servers {
+    // One of the arguments from this list "consul_service custom_endpoint_object k8s_service private_ip private_name public_ip public_name vn_private_ip vn_private_name" must be set
+
+    public_name {
+      dns_name         = "origin.example.com"
+      refresh_interval = 60
+    }
+
+    labels = {
+      "app" = "backend"
+    }
+  }
+
+  origin_servers {
+    // One of the arguments from this list "consul_service custom_endpoint_object k8s_service private_ip private_name public_ip public_name vn_private_ip vn_private_name" must be set
+
+    k8s_service {
+      service_name = "backend-svc"
+
+      // One of the arguments from this list "inside_network outside_network vk8s_networks" must be set
+
+      vk8s_networks {}
+
+      site_locator {
+        // One of the arguments from this list "site virtual_site" must be set
+
+        site {
+          name      = "example-site"
+          namespace = "system"
+        }
+      }
+    }
+  }
+
+  port = 443
+
+  // One of the arguments from this list "no_tls use_tls" must be set
+
+  use_tls {
+    // One of the arguments from this list "disable_sni sni use_host_header_as_sni" must be set
+
+    sni = "backend.example.com"
+
+    tls_config {
+      // One of the arguments from this list "custom_security default_security low_security medium_security" must be set
+
+      default_security {}
+    }
+
+    // One of the arguments from this list "no_mtls use_mtls use_mtls_obj" must be set
+
+    no_mtls {}
+
+    // One of the arguments from this list "skip_server_verification use_server_verification volterra_trusted_ca" must be set
+
+    volterra_trusted_ca {}
+  }
+
+  // Health check configuration
+  healthcheck {
+    name      = "example-healthcheck"
+    namespace = "staging"
+  }
+
+  // Load balancing configuration
+  endpoint_selection     = "LOCAL_PREFERRED"
+  loadbalancer_algorithm = "ROUND_ROBIN"
+}
+```
+
+<!-- schema generated by tfplugindocs -->
+## Argument Reference
+
+### Metadata Argument Reference
+
+<a id="name"></a>&#x2022; [`name`](#name) - Required String<br>Name of the Origin Pool. Must be unique within the namespace
+
+<a id="namespace"></a>&#x2022; [`namespace`](#namespace) - Required String<br>Namespace where the Origin Pool 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="advanced-options"></a>&#x2022; [`advanced_options`](#advanced-options) - Optional Block  Defaults to `null`<br>Origin Pool Advanced Options. Configure Advanced options for origin pool<br>See [Advanced Options](#advanced-options) below for details.
+
+-> **One of the following:**
+&#x2022; <a id="automatic-port"></a>[`automatic_port`](#automatic-port) - Optional Block<br>Enable this option
+<br><br>&#x2022; <a id="lb-port"></a>[`lb_port`](#lb-port) - Optional Block<br>Enable this option
+<br><br>&#x2022; <a id="port"></a>[`port`](#port) - Optional Number<br>Port. Endpoint service is available on this port
+
+<a id="endpoint-selection"></a>&#x2022; [`endpoint_selection`](#endpoint-selection) - Optional String  Defaults to `DISTRIBUTED`<br>Possible values are `DISTRIBUTED`, `LOCAL_ONLY`, `LOCAL_PREFERRED`<br>[Enum: DISTRIBUTED|LOCAL_ONLY|LOCAL_PREFERRED] Endpoint Selection Policy. Policy for selection of endpoints from local site/remote site/both Consider both remote and local endpoints for load balancing LOCAL_ONLY: Consider only local endpoints for load balancing Enable this policy to load balance ONLY among locally discovered endpoints Prefer the local endpoints for load balancing. If local endpoints are not present remote endpoints will be considered
+
+-> **One of the following:**
+&#x2022; <a id="health-check-port"></a>[`health_check_port`](#health-check-port) - Optional Number<br>Health check port. Port used for performing health check
+<br><br>&#x2022; <a id="same-as-endpoint-port"></a>[`same_as_endpoint_port`](#same-as-endpoint-port) - Optional Block<br>Enable this option
+
+<a id="healthcheck"></a>&#x2022; [`healthcheck`](#healthcheck) - Optional Block<br>Health Check object. Reference to healthcheck configuration objects<br>See [Healthcheck](#healthcheck) below for details.
+
+<a id="loadbalancer-algorithm"></a>&#x2022; [`loadbalancer_algorithm`](#loadbalancer-algorithm) - Optional String  Defaults to `ROUND_ROBIN`<br>Possible values are `ROUND_ROBIN`, `LEAST_REQUEST`, `RING_HASH`, `RANDOM`, `LB_OVERRIDE`<br>[Enum: ROUND_ROBIN|LEAST_REQUEST|RING_HASH|RANDOM|LB_OVERRIDE] Load Balancer Algorithm. Different load balancing algorithms supported When a connection to a endpoint in an upstream cluster is required, the load balancer uses loadbalancer_algorithm to determine which host is selected. - ROUND_ROBIN: ROUND_ROBIN Policy in which each healthy/available upstream endpoint is selected in round robin order. - LEAST_REQUEST: LEAST_REQUEST Policy in which loadbalancer picks the upstream endpoint which has the fewest active requests - RING_HASH: RING_HASH Policy implements consistent hashing to upstream endpoints using ring hash of endpoint names Hash of the incoming request is calculated using request hash policy. The ring/modulo hash load balancer implements consistent hashing to upstream hosts. The algorithm is based on mapping all hosts onto a circle such that the addition or removal of a host from the host set changes only affect 1/N requests. This technique is also commonly known as “ketama” hashing. A consistent hashing load balancer is only effective when protocol routing is used that specifies a value to hash on. The minimum ring size governs the replication factor for each host in the ring. For example, if the minimum ring size is 1024 and there are 16 hosts, each host will be replicated 64 times. - RANDOM: RANDOM Policy in which each available upstream endpoint is selected in random order. The random load balancer selects a random healthy host. The random load balancer generally performs better than round robin if no health checking policy is configured. Random selection avoids bias towards the host in the set that comes after a failed host. - LB_OVERRIDE: Load Balancer Override Hash policy is taken from from the load balancer which is using this origin pool
+
+-> **One of the following:**
+&#x2022; <a id="no-tls"></a>[`no_tls`](#no-tls) - Optional Block<br>Enable this option
+
+<a id="origin-servers"></a>&#x2022; [`origin_servers`](#origin-servers) - Optional Block<br>Origin Servers. List of origin servers in this pool<br>See [Origin Servers](#origin-servers) below for details.
+
+<a id="timeouts"></a>&#x2022; [`timeouts`](#timeouts) - Optional Block
+
+<a id="upstream-conn-pool-reuse-type"></a>&#x2022; [`upstream_conn_pool_reuse_type`](#upstream-conn-pool-reuse-type) - Optional Block  Defaults to `null`<br>Select upstream connection pool reuse state. Select upstream connection pool reuse state for every downstream connection. This configuration choice is for HTTP(S) LB only
+
+<a id="use-tls"></a>&#x2022; [`use_tls`](#use-tls) - Optional Block<br>TLS Parameters for Origin Servers. Upstream TLS Parameters
+
+### 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
+
+---
+
+#### Advanced Options
+
+An [`advanced_options`](#advanced-options) block supports the following:
+
+<a id="advanced-options-auto-http-config"></a>&#x2022; [`auto_http_config`](#advanced-options-auto-http-config) - Optional Block<br>Enable this option
+
+<a id="advanced-options-circuit-breaker"></a>&#x2022; [`circuit_breaker`](#advanced-options-circuit-breaker) - Optional Block<br>Circuit Breaker. CircuitBreaker provides a mechanism for watching failures in upstream connections or requests and if the failures reach a certain threshold, automatically fail subsequent requests which allows to apply back pressure on downstream quickly<br>See [Circuit Breaker](#advanced-options-circuit-breaker) below.
+
+<a id="advanced-options-connection-timeout"></a>&#x2022; [`connection_timeout`](#advanced-options-connection-timeout) - Optional Number  Defaults to `2`  Specified in milliseconds<br>Connection Timeout. The timeout for new network connections to endpoints in the cluster.  The seconds
+
+<a id="advanced-options-default-circuit-breaker"></a>&#x2022; [`default_circuit_breaker`](#advanced-options-default-circuit-breaker) - Optional Block<br>Enable this option
+
+<a id="advanced-options-disable-circuit-breaker"></a>&#x2022; [`disable_circuit_breaker`](#advanced-options-disable-circuit-breaker) - Optional Block<br>Enable this option
+
+<a id="advanced-options-disable-lb-source-ip-persistance"></a>&#x2022; [`disable_lb_source_ip_persistance`](#advanced-options-disable-lb-source-ip-persistance) - Optional Block<br>Enable this option
+
+<a id="advanced-options-disable-outlier-detection"></a>&#x2022; [`disable_outlier_detection`](#advanced-options-disable-outlier-detection) - Optional Block<br>Enable this option
+
+<a id="advanced-options-disable-proxy-protocol"></a>&#x2022; [`disable_proxy_protocol`](#advanced-options-disable-proxy-protocol) - Optional Block<br>Enable this option
+
+<a id="advanced-options-disable-subsets"></a>&#x2022; [`disable_subsets`](#advanced-options-disable-subsets) - Optional Block<br>Enable this option
+
+<a id="advanced-options-enable-lb-source-ip-persistance"></a>&#x2022; [`enable_lb_source_ip_persistance`](#advanced-options-enable-lb-source-ip-persistance) - Optional Block<br>Enable this option
+
+<a id="advanced-options-enable-subsets"></a>&#x2022; [`enable_subsets`](#advanced-options-enable-subsets) - Optional Block<br>Origin Pool Subset Options. Configure subset options for origin pool<br>See [Enable Subsets](#advanced-options-enable-subsets) below.
+
+<a id="advanced-options-http1-config"></a>&#x2022; [`http1_config`](#advanced-options-http1-config) - Optional Block<br>HTTP/1.1 Protocol Options. HTTP/1.1 Protocol options for upstream connections<br>See [Http1 Config](#advanced-options-http1-config) below.
+
+<a id="advanced-options-http2-options"></a>&#x2022; [`http2_options`](#advanced-options-http2-options) - Optional Block<br>Http2 Protocol Options. Http2 Protocol options for upstream connections<br>See [Http2 Options](#advanced-options-http2-options) below.
+
+<a id="advanced-options-http-idle-timeout"></a>&#x2022; [`http_idle_timeout`](#advanced-options-http-idle-timeout) - Optional Number  Defaults to `5`  Specified in milliseconds<br>HTTP Idle Timeout. The idle timeout for upstream connection pool connections. The idle timeout is defined as the period in which there are no active requests. When the idle timeout is reached the connection will be closed. Note that request based timeouts mean that HTTP/2 PINGs will not keep the connection alive.  The minutes
+
+<a id="advanced-options-no-panic-threshold"></a>&#x2022; [`no_panic_threshold`](#advanced-options-no-panic-threshold) - Optional Block<br>Enable this option
+
+<a id="advanced-options-outlier-detection"></a>&#x2022; [`outlier_detection`](#advanced-options-outlier-detection) - Optional Block<br>Outlier Detection. Outlier detection and ejection is the process of dynamically determining whether some number of hosts in an upstream cluster are performing unlike the others and removing them from the healthy load balancing set. Outlier detection is a form of passive health checking. Algorithm 1. A endpoint is determined to be an outlier (based on configured number of consecutive_5xx or consecutive_gateway_failures) . 2. If no endpoints have been ejected, loadbalancer will eject the host immediately. Otherwise, it checks to make sure the number of ejected hosts is below the allowed threshold (specified via max_ejection_percent setting). If the number of ejected hosts is above the threshold, the host is not ejected. 3. The endpoint is ejected for some number of milliseconds. Ejection means that the endpoint is marked unhealthy and will not be used during load balancing. The number of milliseconds is equal to the base_ejection_time value multiplied by the number of times the host has been ejected. 4. An ejected endpoint will automatically be brought back into service after the ejection time has been satisfied<br>See [Outlier Detection](#advanced-options-outlier-detection) below.
+
+<a id="advanced-options-panic-threshold"></a>&#x2022; [`panic_threshold`](#advanced-options-panic-threshold) - Optional Number<br>Panic threshold. Configure a threshold (percentage of unhealthy endpoints) below which all endpoints will be considered for load balancing ignoring its health status
+
+<a id="advanced-options-proxy-protocol-v1"></a>&#x2022; [`proxy_protocol_v1`](#advanced-options-proxy-protocol-v1) - Optional Block<br>Enable this option
+
+<a id="advanced-options-proxy-protocol-v2"></a>&#x2022; [`proxy_protocol_v2`](#advanced-options-proxy-protocol-v2) - Optional Block<br>Enable this option
+
+#### Advanced Options Circuit Breaker
+
+A [`circuit_breaker`](#advanced-options-circuit-breaker) block (within [`advanced_options`](#advanced-options)) supports the following:
+
+<a id="advanced-options-circuit-breaker-connection-limit"></a>&#x2022; [`connection_limit`](#advanced-options-circuit-breaker-connection-limit) - Optional Number<br>Connection Limit. The maximum number of connections that loadbalancer will establish to all hosts in an upstream cluster. In practice this is only applicable to TCP and HTTP/1.1 clusters since HTTP/2 uses a single connection to each host. Remove endpoint out of load balancing decision, if number of connections reach connection limit
+
+<a id="advanced-options-circuit-breaker-max-requests"></a>&#x2022; [`max_requests`](#advanced-options-circuit-breaker-max-requests) - Optional Number<br>Maximum Request Count. The maximum number of requests that can be outstanding to all hosts in a cluster at any given time. In practice this is applicable to HTTP/2 clusters since HTTP/1.1 clusters are governed by the maximum connections (connection_limit). Remove endpoint out of load balancing decision, if requests exceed this count
+
+<a id="advanced-options-circuit-breaker-pending-requests"></a>&#x2022; [`pending_requests`](#advanced-options-circuit-breaker-pending-requests) - Optional Number<br>Pending Requests. The maximum number of requests that will be queued while waiting for a ready connection pool connection. Since HTTP/2 requests are sent over a single connection, this circuit breaker only comes into play as the initial connection is created, as requests will be multiplexed immediately afterwards. For HTTP/1.1, requests are added to the list of pending requests whenever there aren’t enough upstream connections available to immediately dispatch the request, so this circuit breaker will remain in play for the lifetime of the process. Remove endpoint out of load balancing decision, if pending request reach pending_request
+
+<a id="advanced-options-circuit-breaker-priority"></a>&#x2022; [`priority`](#advanced-options-circuit-breaker-priority) - Optional String  Defaults to `DEFAULT`<br>Possible values are `DEFAULT`, `HIGH`<br>[Enum: DEFAULT|HIGH] Routing Priority. Priority routing for each request. Different connection pools are used based on the priority selected for the request. Also, circuit-breaker configuration at destination cluster is chosen based on selected priority. Default routing mechanism High-Priority routing mechanism
+
+<a id="advanced-options-circuit-breaker-retries"></a>&#x2022; [`retries`](#advanced-options-circuit-breaker-retries) - Optional Number<br>Retry Count. The maximum number of retries that can be outstanding to all hosts in a cluster at any given time. Remove endpoint out of load balancing decision, if retries for request exceed this count
+
+#### Advanced Options Enable Subsets
+
+An [`enable_subsets`](#advanced-options-enable-subsets) block (within [`advanced_options`](#advanced-options)) supports the following:
+
+<a id="advanced-options-enable-subsets-any-endpoint"></a>&#x2022; [`any_endpoint`](#advanced-options-enable-subsets-any-endpoint) - Optional Block<br>Enable this option
+
+<a id="advanced-options-enable-subsets-default-subset"></a>&#x2022; [`default_subset`](#advanced-options-enable-subsets-default-subset) - Optional Block<br>Origin Pool Default Subset. Default Subset definition<br>See [Default Subset](#advanced-options-enable-subsets-default-subset) below.
+
+<a id="advanced-options-enable-subsets-endpoint-subsets"></a>&#x2022; [`endpoint_subsets`](#advanced-options-enable-subsets-endpoint-subsets) - Optional Block<br>Origin Server Subsets Classes. List of subset class. Subsets class is defined using list of keys. Every unique combination of values of these keys form a subset withing the class<br>See [Endpoint Subsets](#advanced-options-enable-subsets-endpoint-subsets) below.
+
+<a id="advanced-options-enable-subsets-fail-request"></a>&#x2022; [`fail_request`](#advanced-options-enable-subsets-fail-request) - Optional Block<br>Enable this option
+
+#### Advanced Options Enable Subsets Default Subset
+
+A [`default_subset`](#advanced-options-enable-subsets-default-subset) block (within [`advanced_options.enable_subsets`](#advanced-options-enable-subsets)) supports the following:
+
+<a id="advanced-options-enable-subsets-default-subset-default-subset"></a>&#x2022; [`default_subset`](#advanced-options-enable-subsets-default-subset-default-subset) - Optional Block<br>Default Subset for Origin Pool. List of key-value pairs that define default subset. which gets used when route specifies no metadata or no subset matching the metadata exists
+
+#### Advanced Options Enable Subsets Endpoint Subsets
+
+An [`endpoint_subsets`](#advanced-options-enable-subsets-endpoint-subsets) block (within [`advanced_options.enable_subsets`](#advanced-options-enable-subsets)) supports the following:
+
+<a id="advanced-options-enable-subsets-endpoint-subsets-keys"></a>&#x2022; [`keys`](#advanced-options-enable-subsets-endpoint-subsets-keys) - Optional List<br>Keys. List of keys that define a cluster subset class
+
+#### Advanced Options Http1 Config
+
+A [`http1_config`](#advanced-options-http1-config) block (within [`advanced_options`](#advanced-options)) supports the following:
+
+<a id="advanced-options-http1-config-header-transformation"></a>&#x2022; [`header_transformation`](#advanced-options-http1-config-header-transformation) - Optional Block<br>Header Transformation. Header Transformation options for HTTP/1.1 request/response headers<br>See [Header Transformation](#advanced-options-http1-config-header-transformation) below.
+
+#### Advanced Options Http1 Config Header Transformation
+
+A [`header_transformation`](#advanced-options-http1-config-header-transformation) block (within [`advanced_options.http1_config`](#advanced-options-http1-config)) supports the following:
+
+<a id="advanced-options-http1-config-header-transformation-default-header-transformation"></a>&#x2022; [`default_header_transformation`](#advanced-options-http1-config-header-transformation-default-header-transformation) - Optional Block<br>Enable this option
+
+<a id="advanced-options-http1-config-header-transformation-legacy-header-transformation"></a>&#x2022; [`legacy_header_transformation`](#advanced-options-http1-config-header-transformation-legacy-header-transformation) - Optional Block<br>Enable this option
+
+<a id="advanced-options-http1-config-header-transformation-preserve-case-header-transformation"></a>&#x2022; [`preserve_case_header_transformation`](#advanced-options-http1-config-header-transformation-preserve-case-header-transformation) - Optional Block<br>Enable this option
+
+<a id="advanced-options-http1-config-header-transformation-proper-case-header-transformation"></a>&#x2022; [`proper_case_header_transformation`](#advanced-options-http1-config-header-transformation-proper-case-header-transformation) - Optional Block<br>Enable this option
+
+#### Advanced Options Http2 Options
+
+A [`http2_options`](#advanced-options-http2-options) block (within [`advanced_options`](#advanced-options)) supports the following:
+
+<a id="advanced-options-http2-options-enabled"></a>&#x2022; [`enabled`](#advanced-options-http2-options-enabled) - Optional Bool<br>HTTP2 Enabled. Enable/disable HTTP2 Protocol for upstream connections
+
+#### Advanced Options Outlier Detection
+
+An [`outlier_detection`](#advanced-options-outlier-detection) block (within [`advanced_options`](#advanced-options)) supports the following:
+
+<a id="advanced-options-outlier-detection-base-ejection-time"></a>&#x2022; [`base_ejection_time`](#advanced-options-outlier-detection-base-ejection-time) - Optional Number  Defaults to `30000ms`  Specified in milliseconds<br>Base Ejection Time. The base time that a host is ejected for. The real time is equal to the base time multiplied by the number of times the host has been ejected. This causes hosts to get ejected for longer periods if they continue to fail
+
+<a id="advanced-options-outlier-detection-consecutive-5xx"></a>&#x2022; [`consecutive_5xx`](#advanced-options-outlier-detection-consecutive-5xx) - Optional Number  Defaults to `5`<br>Consecutive 5xx Count. If an upstream endpoint returns some number of consecutive 5xx, it will be ejected. Note that in this case a 5xx means an actual 5xx respond code, or an event that would cause the HTTP router to return one on the upstream’s behalf(reset, connection failure, etc.) consecutive_5xx indicates the number of consecutive 5xx responses required before a consecutive 5xx ejection occurs
+
+<a id="advanced-options-outlier-detection-consecutive-gateway-failure"></a>&#x2022; [`consecutive_gateway_failure`](#advanced-options-outlier-detection-consecutive-gateway-failure) - Optional Number  Defaults to `5`<br>Consecutive Gateway Failure. If an upstream endpoint returns some number of consecutive “gateway errors” (502, 503 or 504 status code), it will be ejected. Note that this includes events that would cause the HTTP router to return one of these status codes on the upstream’s behalf (reset, connection failure, etc.). consecutive_gateway_failure indicates the number of consecutive gateway failures before a consecutive gateway failure ejection occurs
+
+<a id="advanced-options-outlier-detection-interval"></a>&#x2022; [`interval`](#advanced-options-outlier-detection-interval) - Optional Number  Defaults to `10000ms`  Specified in milliseconds<br>Interval. The time interval between ejection analysis sweeps. This can result in both new ejections as well as endpoints being returned to service
+
+<a id="advanced-options-outlier-detection-max-ejection-percent"></a>&#x2022; [`max_ejection_percent`](#advanced-options-outlier-detection-max-ejection-percent) - Optional Number  Defaults to `10%`<br>Max Ejection Percentage. The maximum % of an upstream cluster that can be ejected due to outlier detection. but will eject at least one host regardless of the value
+
+#### Healthcheck
+
+A [`healthcheck`](#healthcheck) block supports the following:
+
+<a id="healthcheck-name"></a>&#x2022; [`name`](#healthcheck-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="healthcheck-namespace"></a>&#x2022; [`namespace`](#healthcheck-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="healthcheck-tenant"></a>&#x2022; [`tenant`](#healthcheck-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 Servers
+
+An [`origin_servers`](#origin-servers) block supports the following:
+
+<a id="origin-servers-cbip-service"></a>&#x2022; [`cbip_service`](#origin-servers-cbip-service) - Optional Block<br>Discovered Classic BIG-IP Service Name. Specify origin server with Classic BIG-IP Service (Virtual Server)<br>See [Cbip Service](#origin-servers-cbip-service) below.
+
+<a id="origin-servers-consul-service"></a>&#x2022; [`consul_service`](#origin-servers-consul-service) - Optional Block<br>Consul Service Name on given Sites. Specify origin server with Hashi Corp Consul service name and site information<br>See [Consul Service](#origin-servers-consul-service) below.
+
+<a id="origin-servers-custom-endpoint-object"></a>&#x2022; [`custom_endpoint_object`](#origin-servers-custom-endpoint-object) - Optional Block<br>Custom Endpoint Object for Origin Server. Specify origin server with a reference to endpoint object<br>See [Custom Endpoint Object](#origin-servers-custom-endpoint-object) below.
+
+<a id="origin-servers-k8s-service"></a>&#x2022; [`k8s_service`](#origin-servers-k8s-service) - Optional Block<br>K8S Service Name on given Sites. Specify origin server with K8S service name and site information<br>See [K8S Service](#origin-servers-k8s-service) below.
+
+<a id="origin-servers-labels"></a>&#x2022; [`labels`](#origin-servers-labels) - Optional Block<br>Origin Server Labels. Add Labels for this origin server, these labels can be used to form subset
+
+<a id="origin-servers-private-ip"></a>&#x2022; [`private_ip`](#origin-servers-private-ip) - Optional Block<br>IP address on given Sites. Specify origin server with private or public IP address and site information<br>See [Private IP](#origin-servers-private-ip) below.
+
+<a id="origin-servers-private-name"></a>&#x2022; [`private_name`](#origin-servers-private-name) - Optional Block<br>DNS Name on given Sites. Specify origin server with private or public DNS name and site information<br>See [Private Name](#origin-servers-private-name) below.
+
+<a id="origin-servers-public-ip"></a>&#x2022; [`public_ip`](#origin-servers-public-ip) - Optional Block<br>Public IP. Specify origin server with public IP address<br>See [Public IP](#origin-servers-public-ip) below.
+
+<a id="origin-servers-public-name"></a>&#x2022; [`public_name`](#origin-servers-public-name) - Optional Block<br>Public DNS Name. Specify origin server with public DNS name<br>See [Public Name](#origin-servers-public-name) below.
+
+<a id="origin-servers-vn-private-ip"></a>&#x2022; [`vn_private_ip`](#origin-servers-vn-private-ip) - Optional Block<br>IP address Virtual Network. Specify origin server with IP on Virtual Network<br>See [Vn Private IP](#origin-servers-vn-private-ip) below.
+
+<a id="origin-servers-vn-private-name"></a>&#x2022; [`vn_private_name`](#origin-servers-vn-private-name) - Optional Block<br>DNS Name on Virtual Network. Specify origin server with DNS name on Virtual Network<br>See [Vn Private Name](#origin-servers-vn-private-name) below.
+
+#### Origin Servers Cbip Service
+
+A [`cbip_service`](#origin-servers-cbip-service) block (within [`origin_servers`](#origin-servers)) supports the following:
+
+<a id="origin-servers-cbip-service-service-name"></a>&#x2022; [`service_name`](#origin-servers-cbip-service-service-name) - Optional String<br>Service Name. Name of the discovered Classic BIG-IP virtual server to be used as origin
+
+#### Origin Servers Consul Service
+
+A [`consul_service`](#origin-servers-consul-service) block (within [`origin_servers`](#origin-servers)) supports the following:
+
+<a id="origin-servers-consul-service-inside-network"></a>&#x2022; [`inside_network`](#origin-servers-consul-service-inside-network) - Optional Block<br>Enable this option
+
+<a id="origin-servers-consul-service-outside-network"></a>&#x2022; [`outside_network`](#origin-servers-consul-service-outside-network) - Optional Block<br>Enable this option
+
+<a id="origin-servers-consul-service-service-name"></a>&#x2022; [`service_name`](#origin-servers-consul-service-service-name) - Optional String<br>Service Name. Consul service name of this origin server will be listed, including cluster-ID. The format is servicename:cluster-ID
+
+<a id="origin-servers-consul-service-site-locator"></a>&#x2022; [`site_locator`](#origin-servers-consul-service-site-locator) - Optional Block<br>Site or Virtual Site. This message defines a reference to a site or virtual site object<br>See [Site Locator](#origin-servers-consul-service-site-locator) below.
+
+<a id="origin-servers-consul-service-snat-pool"></a>&#x2022; [`snat_pool`](#origin-servers-consul-service-snat-pool) - Optional Block<br>Snat Pool. Snat Pool configuration<br>See [Snat Pool](#origin-servers-consul-service-snat-pool) below.
+
+#### Origin Servers Consul Service Site Locator
+
+A [`site_locator`](#origin-servers-consul-service-site-locator) block (within [`origin_servers.consul_service`](#origin-servers-consul-service)) supports the following:
+
+<a id="origin-servers-consul-service-site-locator-site"></a>&#x2022; [`site`](#origin-servers-consul-service-site-locator-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](#origin-servers-consul-service-site-locator-site) below.
+
+<a id="origin-servers-consul-service-site-locator-virtual-site"></a>&#x2022; [`virtual_site`](#origin-servers-consul-service-site-locator-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](#origin-servers-consul-service-site-locator-virtual-site) below.
+
+#### Origin Servers Consul Service Site Locator Site
+
+A [`site`](#origin-servers-consul-service-site-locator-site) block (within [`origin_servers.consul_service.site_locator`](#origin-servers-consul-service-site-locator)) supports the following:
+
+<a id="origin-servers-consul-service-site-locator-site-name"></a>&#x2022; [`name`](#origin-servers-consul-service-site-locator-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="origin-servers-consul-service-site-locator-site-namespace"></a>&#x2022; [`namespace`](#origin-servers-consul-service-site-locator-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="origin-servers-consul-service-site-locator-site-tenant"></a>&#x2022; [`tenant`](#origin-servers-consul-service-site-locator-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
+
+#### Origin Servers Consul Service Site Locator Virtual Site
+
+A [`virtual_site`](#origin-servers-consul-service-site-locator-virtual-site) block (within [`origin_servers.consul_service.site_locator`](#origin-servers-consul-service-site-locator)) supports the following:
+
+<a id="origin-servers-consul-service-site-locator-virtual-site-name"></a>&#x2022; [`name`](#origin-servers-consul-service-site-locator-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="origin-servers-consul-service-site-locator-virtual-site-namespace"></a>&#x2022; [`namespace`](#origin-servers-consul-service-site-locator-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="origin-servers-consul-service-site-locator-virtual-site-tenant"></a>&#x2022; [`tenant`](#origin-servers-consul-service-site-locator-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
+
+#### Origin Servers Consul Service Snat Pool
+
+A [`snat_pool`](#origin-servers-consul-service-snat-pool) block (within [`origin_servers.consul_service`](#origin-servers-consul-service)) supports the following:
+
+<a id="origin-servers-consul-service-snat-pool-no-snat-pool"></a>&#x2022; [`no_snat_pool`](#origin-servers-consul-service-snat-pool-no-snat-pool) - Optional Block<br>Enable this option
+
+<a id="origin-servers-consul-service-snat-pool-snat-pool"></a>&#x2022; [`snat_pool`](#origin-servers-consul-service-snat-pool-snat-pool) - Optional Block<br>IPv4 Prefix List. List of IPv4 prefixes that represent an endpoint<br>See [Snat Pool](#origin-servers-consul-service-snat-pool-snat-pool) below.
+
+#### Origin Servers Consul Service Snat Pool Snat Pool
+
+A [`snat_pool`](#origin-servers-consul-service-snat-pool-snat-pool) block (within [`origin_servers.consul_service.snat_pool`](#origin-servers-consul-service-snat-pool)) supports the following:
+
+<a id="origin-servers-consul-service-snat-pool-snat-pool-prefixes"></a>&#x2022; [`prefixes`](#origin-servers-consul-service-snat-pool-snat-pool-prefixes) - Optional List<br>IPv4 Prefix List. List of IPv4 prefixes that represent an endpoint
+
+#### Origin Servers Custom Endpoint Object
+
+A [`custom_endpoint_object`](#origin-servers-custom-endpoint-object) block (within [`origin_servers`](#origin-servers)) supports the following:
+
+<a id="origin-servers-custom-endpoint-object-endpoint"></a>&#x2022; [`endpoint`](#origin-servers-custom-endpoint-object-endpoint) - 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 [Endpoint](#origin-servers-custom-endpoint-object-endpoint) below.
+
+#### Origin Servers Custom Endpoint Object Endpoint
+
+An [`endpoint`](#origin-servers-custom-endpoint-object-endpoint) block (within [`origin_servers.custom_endpoint_object`](#origin-servers-custom-endpoint-object)) supports the following:
+
+<a id="origin-servers-custom-endpoint-object-endpoint-name"></a>&#x2022; [`name`](#origin-servers-custom-endpoint-object-endpoint-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-servers-custom-endpoint-object-endpoint-namespace"></a>&#x2022; [`namespace`](#origin-servers-custom-endpoint-object-endpoint-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-servers-custom-endpoint-object-endpoint-tenant"></a>&#x2022; [`tenant`](#origin-servers-custom-endpoint-object-endpoint-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 Servers K8S Service
+
+A [`k8s_service`](#origin-servers-k8s-service) block (within [`origin_servers`](#origin-servers)) supports the following:
+
+<a id="origin-servers-k8s-service-inside-network"></a>&#x2022; [`inside_network`](#origin-servers-k8s-service-inside-network) - Optional Block<br>Enable this option
+
+<a id="origin-servers-k8s-service-outside-network"></a>&#x2022; [`outside_network`](#origin-servers-k8s-service-outside-network) - Optional Block<br>Enable this option
+
+<a id="origin-servers-k8s-service-protocol"></a>&#x2022; [`protocol`](#origin-servers-k8s-service-protocol) - Optional String  Defaults to `PROTOCOL_TCP`<br>Possible values are `PROTOCOL_TCP`, `PROTOCOL_UDP`<br>[Enum: PROTOCOL_TCP|PROTOCOL_UDP] Protocol Type. Type of protocol - PROTOCOL_TCP: TCP - PROTOCOL_UDP: UDP
+
+<a id="origin-servers-k8s-service-service-name"></a>&#x2022; [`service_name`](#origin-servers-k8s-service-service-name) - Optional String<br>Service Name. K8S service name of the origin server will be listed, including the namespace and cluster-ID. For vK8s services, you need to enter a string with the format servicename.namespace:cluster-ID. If the servicename is 'frontend', namespace is 'speedtest' and cluster-ID is 'prod', then you will enter 'frontend.speedtest:prod'. Both namespace and cluster-ID are optional
+
+<a id="origin-servers-k8s-service-site-locator"></a>&#x2022; [`site_locator`](#origin-servers-k8s-service-site-locator) - Optional Block<br>Site or Virtual Site. This message defines a reference to a site or virtual site object<br>See [Site Locator](#origin-servers-k8s-service-site-locator) below.
+
+<a id="origin-servers-k8s-service-snat-pool"></a>&#x2022; [`snat_pool`](#origin-servers-k8s-service-snat-pool) - Optional Block<br>Snat Pool. Snat Pool configuration<br>See [Snat Pool](#origin-servers-k8s-service-snat-pool) below.
+
+<a id="origin-servers-k8s-service-vk8s-networks"></a>&#x2022; [`vk8s_networks`](#origin-servers-k8s-service-vk8s-networks) - Optional Block<br>Enable this option
+
+#### Origin Servers K8S Service Site Locator
+
+A [`site_locator`](#origin-servers-k8s-service-site-locator) block (within [`origin_servers.k8s_service`](#origin-servers-k8s-service)) supports the following:
+
+<a id="origin-servers-k8s-service-site-locator-site"></a>&#x2022; [`site`](#origin-servers-k8s-service-site-locator-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](#origin-servers-k8s-service-site-locator-site) below.
+
+<a id="origin-servers-k8s-service-site-locator-virtual-site"></a>&#x2022; [`virtual_site`](#origin-servers-k8s-service-site-locator-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](#origin-servers-k8s-service-site-locator-virtual-site) below.
+
+#### Origin Servers K8S Service Site Locator Site
+
+A [`site`](#origin-servers-k8s-service-site-locator-site) block (within [`origin_servers.k8s_service.site_locator`](#origin-servers-k8s-service-site-locator)) supports the following:
+
+<a id="origin-servers-k8s-service-site-locator-site-name"></a>&#x2022; [`name`](#origin-servers-k8s-service-site-locator-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="origin-servers-k8s-service-site-locator-site-namespace"></a>&#x2022; [`namespace`](#origin-servers-k8s-service-site-locator-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="origin-servers-k8s-service-site-locator-site-tenant"></a>&#x2022; [`tenant`](#origin-servers-k8s-service-site-locator-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
+
+#### Origin Servers K8S Service Site Locator Virtual Site
+
+A [`virtual_site`](#origin-servers-k8s-service-site-locator-virtual-site) block (within [`origin_servers.k8s_service.site_locator`](#origin-servers-k8s-service-site-locator)) supports the following:
+
+<a id="origin-servers-k8s-service-site-locator-virtual-site-name"></a>&#x2022; [`name`](#origin-servers-k8s-service-site-locator-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="origin-servers-k8s-service-site-locator-virtual-site-namespace"></a>&#x2022; [`namespace`](#origin-servers-k8s-service-site-locator-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="origin-servers-k8s-service-site-locator-virtual-site-tenant"></a>&#x2022; [`tenant`](#origin-servers-k8s-service-site-locator-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
+
+#### Origin Servers K8S Service Snat Pool
+
+A [`snat_pool`](#origin-servers-k8s-service-snat-pool) block (within [`origin_servers.k8s_service`](#origin-servers-k8s-service)) supports the following:
+
+<a id="origin-servers-k8s-service-snat-pool-no-snat-pool"></a>&#x2022; [`no_snat_pool`](#origin-servers-k8s-service-snat-pool-no-snat-pool) - Optional Block<br>Enable this option
+
+<a id="origin-servers-k8s-service-snat-pool-snat-pool"></a>&#x2022; [`snat_pool`](#origin-servers-k8s-service-snat-pool-snat-pool) - Optional Block<br>IPv4 Prefix List. List of IPv4 prefixes that represent an endpoint<br>See [Snat Pool](#origin-servers-k8s-service-snat-pool-snat-pool) below.
+
+#### Origin Servers K8S Service Snat Pool Snat Pool
+
+A [`snat_pool`](#origin-servers-k8s-service-snat-pool-snat-pool) block (within [`origin_servers.k8s_service.snat_pool`](#origin-servers-k8s-service-snat-pool)) supports the following:
+
+<a id="origin-servers-k8s-service-snat-pool-snat-pool-prefixes"></a>&#x2022; [`prefixes`](#origin-servers-k8s-service-snat-pool-snat-pool-prefixes) - Optional List<br>IPv4 Prefix List. List of IPv4 prefixes that represent an endpoint
+
+#### Origin Servers Private IP
+
+A [`private_ip`](#origin-servers-private-ip) block (within [`origin_servers`](#origin-servers)) supports the following:
+
+<a id="origin-servers-private-ip-inside-network"></a>&#x2022; [`inside_network`](#origin-servers-private-ip-inside-network) - Optional Block<br>Enable this option
+
+<a id="origin-servers-private-ip-ip"></a>&#x2022; [`ip`](#origin-servers-private-ip-ip) - Optional String<br>IP. Private IPv4 address
+
+<a id="origin-servers-private-ip-outside-network"></a>&#x2022; [`outside_network`](#origin-servers-private-ip-outside-network) - Optional Block<br>Enable this option
+
+<a id="origin-servers-private-ip-segment"></a>&#x2022; [`segment`](#origin-servers-private-ip-segment) - 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 [Segment](#origin-servers-private-ip-segment) below.
+
+<a id="origin-servers-private-ip-site-locator"></a>&#x2022; [`site_locator`](#origin-servers-private-ip-site-locator) - Optional Block<br>Site or Virtual Site. This message defines a reference to a site or virtual site object<br>See [Site Locator](#origin-servers-private-ip-site-locator) below.
+
+<a id="origin-servers-private-ip-snat-pool"></a>&#x2022; [`snat_pool`](#origin-servers-private-ip-snat-pool) - Optional Block<br>Snat Pool. Snat Pool configuration<br>See [Snat Pool](#origin-servers-private-ip-snat-pool) below.
+
+#### Origin Servers Private IP Segment
+
+A [`segment`](#origin-servers-private-ip-segment) block (within [`origin_servers.private_ip`](#origin-servers-private-ip)) supports the following:
+
+<a id="origin-servers-private-ip-segment-name"></a>&#x2022; [`name`](#origin-servers-private-ip-segment-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-servers-private-ip-segment-namespace"></a>&#x2022; [`namespace`](#origin-servers-private-ip-segment-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-servers-private-ip-segment-tenant"></a>&#x2022; [`tenant`](#origin-servers-private-ip-segment-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 Servers Private IP Site Locator
+
+A [`site_locator`](#origin-servers-private-ip-site-locator) block (within [`origin_servers.private_ip`](#origin-servers-private-ip)) supports the following:
+
+<a id="origin-servers-private-ip-site-locator-site"></a>&#x2022; [`site`](#origin-servers-private-ip-site-locator-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](#origin-servers-private-ip-site-locator-site) below.
+
+<a id="origin-servers-private-ip-site-locator-virtual-site"></a>&#x2022; [`virtual_site`](#origin-servers-private-ip-site-locator-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](#origin-servers-private-ip-site-locator-virtual-site) below.
+
+#### Origin Servers Private IP Site Locator Site
+
+A [`site`](#origin-servers-private-ip-site-locator-site) block (within [`origin_servers.private_ip.site_locator`](#origin-servers-private-ip-site-locator)) supports the following:
+
+<a id="origin-servers-private-ip-site-locator-site-name"></a>&#x2022; [`name`](#origin-servers-private-ip-site-locator-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="origin-servers-private-ip-site-locator-site-namespace"></a>&#x2022; [`namespace`](#origin-servers-private-ip-site-locator-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="origin-servers-private-ip-site-locator-site-tenant"></a>&#x2022; [`tenant`](#origin-servers-private-ip-site-locator-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
+
+#### Origin Servers Private IP Site Locator Virtual Site
+
+A [`virtual_site`](#origin-servers-private-ip-site-locator-virtual-site) block (within [`origin_servers.private_ip.site_locator`](#origin-servers-private-ip-site-locator)) supports the following:
+
+<a id="origin-servers-private-ip-site-locator-virtual-site-name"></a>&#x2022; [`name`](#origin-servers-private-ip-site-locator-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="origin-servers-private-ip-site-locator-virtual-site-namespace"></a>&#x2022; [`namespace`](#origin-servers-private-ip-site-locator-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="origin-servers-private-ip-site-locator-virtual-site-tenant"></a>&#x2022; [`tenant`](#origin-servers-private-ip-site-locator-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
+
+#### Origin Servers Private IP Snat Pool
+
+A [`snat_pool`](#origin-servers-private-ip-snat-pool) block (within [`origin_servers.private_ip`](#origin-servers-private-ip)) supports the following:
+
+<a id="origin-servers-private-ip-snat-pool-no-snat-pool"></a>&#x2022; [`no_snat_pool`](#origin-servers-private-ip-snat-pool-no-snat-pool) - Optional Block<br>Enable this option
+
+<a id="origin-servers-private-ip-snat-pool-snat-pool"></a>&#x2022; [`snat_pool`](#origin-servers-private-ip-snat-pool-snat-pool) - Optional Block<br>IPv4 Prefix List. List of IPv4 prefixes that represent an endpoint<br>See [Snat Pool](#origin-servers-private-ip-snat-pool-snat-pool) below.
+
+#### Origin Servers Private IP Snat Pool Snat Pool
+
+A [`snat_pool`](#origin-servers-private-ip-snat-pool-snat-pool) block (within [`origin_servers.private_ip.snat_pool`](#origin-servers-private-ip-snat-pool)) supports the following:
+
+<a id="origin-servers-private-ip-snat-pool-snat-pool-prefixes"></a>&#x2022; [`prefixes`](#origin-servers-private-ip-snat-pool-snat-pool-prefixes) - Optional List<br>IPv4 Prefix List. List of IPv4 prefixes that represent an endpoint
+
+#### Origin Servers Private Name
+
+A [`private_name`](#origin-servers-private-name) block (within [`origin_servers`](#origin-servers)) supports the following:
+
+<a id="origin-servers-private-name-dns-name"></a>&#x2022; [`dns_name`](#origin-servers-private-name-dns-name) - Optional String<br>DNS Name. DNS Name
+
+<a id="origin-servers-private-name-inside-network"></a>&#x2022; [`inside_network`](#origin-servers-private-name-inside-network) - Optional Block<br>Enable this option
+
+<a id="origin-servers-private-name-outside-network"></a>&#x2022; [`outside_network`](#origin-servers-private-name-outside-network) - Optional Block<br>Enable this option
+
+<a id="origin-servers-private-name-refresh-interval"></a>&#x2022; [`refresh_interval`](#origin-servers-private-name-refresh-interval) - Optional Number<br>DNS Refresh Interval. Interval for DNS refresh in seconds. Max value is 7 days as per `HTTPS://datatracker.ietf.org/doc/HTML/rfc8767`
+
+<a id="origin-servers-private-name-segment"></a>&#x2022; [`segment`](#origin-servers-private-name-segment) - 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 [Segment](#origin-servers-private-name-segment) below.
+
+<a id="origin-servers-private-name-site-locator"></a>&#x2022; [`site_locator`](#origin-servers-private-name-site-locator) - Optional Block<br>Site or Virtual Site. This message defines a reference to a site or virtual site object<br>See [Site Locator](#origin-servers-private-name-site-locator) below.
+
+<a id="origin-servers-private-name-snat-pool"></a>&#x2022; [`snat_pool`](#origin-servers-private-name-snat-pool) - Optional Block<br>Snat Pool. Snat Pool configuration<br>See [Snat Pool](#origin-servers-private-name-snat-pool) below.
+
+#### Origin Servers Private Name Segment
+
+A [`segment`](#origin-servers-private-name-segment) block (within [`origin_servers.private_name`](#origin-servers-private-name)) supports the following:
+
+<a id="origin-servers-private-name-segment-name"></a>&#x2022; [`name`](#origin-servers-private-name-segment-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-servers-private-name-segment-namespace"></a>&#x2022; [`namespace`](#origin-servers-private-name-segment-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-servers-private-name-segment-tenant"></a>&#x2022; [`tenant`](#origin-servers-private-name-segment-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 Servers Private Name Site Locator
+
+A [`site_locator`](#origin-servers-private-name-site-locator) block (within [`origin_servers.private_name`](#origin-servers-private-name)) supports the following:
+
+<a id="origin-servers-private-name-site-locator-site"></a>&#x2022; [`site`](#origin-servers-private-name-site-locator-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](#origin-servers-private-name-site-locator-site) below.
+
+<a id="origin-servers-private-name-site-locator-virtual-site"></a>&#x2022; [`virtual_site`](#origin-servers-private-name-site-locator-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](#origin-servers-private-name-site-locator-virtual-site) below.
+
+#### Origin Servers Private Name Site Locator Site
+
+A [`site`](#origin-servers-private-name-site-locator-site) block (within [`origin_servers.private_name.site_locator`](#origin-servers-private-name-site-locator)) supports the following:
+
+<a id="origin-servers-private-name-site-locator-site-name"></a>&#x2022; [`name`](#origin-servers-private-name-site-locator-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="origin-servers-private-name-site-locator-site-namespace"></a>&#x2022; [`namespace`](#origin-servers-private-name-site-locator-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="origin-servers-private-name-site-locator-site-tenant"></a>&#x2022; [`tenant`](#origin-servers-private-name-site-locator-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
+
+#### Origin Servers Private Name Site Locator Virtual Site
+
+A [`virtual_site`](#origin-servers-private-name-site-locator-virtual-site) block (within [`origin_servers.private_name.site_locator`](#origin-servers-private-name-site-locator)) supports the following:
+
+<a id="origin-servers-private-name-site-locator-virtual-site-name"></a>&#x2022; [`name`](#origin-servers-private-name-site-locator-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="origin-servers-private-name-site-locator-virtual-site-namespace"></a>&#x2022; [`namespace`](#origin-servers-private-name-site-locator-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="origin-servers-private-name-site-locator-virtual-site-tenant"></a>&#x2022; [`tenant`](#origin-servers-private-name-site-locator-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
+
+#### Origin Servers Private Name Snat Pool
+
+A [`snat_pool`](#origin-servers-private-name-snat-pool) block (within [`origin_servers.private_name`](#origin-servers-private-name)) supports the following:
+
+<a id="origin-servers-private-name-snat-pool-no-snat-pool"></a>&#x2022; [`no_snat_pool`](#origin-servers-private-name-snat-pool-no-snat-pool) - Optional Block<br>Enable this option
+
+<a id="origin-servers-private-name-snat-pool-snat-pool"></a>&#x2022; [`snat_pool`](#origin-servers-private-name-snat-pool-snat-pool) - Optional Block<br>IPv4 Prefix List. List of IPv4 prefixes that represent an endpoint<br>See [Snat Pool](#origin-servers-private-name-snat-pool-snat-pool) below.
+
+#### Origin Servers Private Name Snat Pool Snat Pool
+
+A [`snat_pool`](#origin-servers-private-name-snat-pool-snat-pool) block (within [`origin_servers.private_name.snat_pool`](#origin-servers-private-name-snat-pool)) supports the following:
+
+<a id="origin-servers-private-name-snat-pool-snat-pool-prefixes"></a>&#x2022; [`prefixes`](#origin-servers-private-name-snat-pool-snat-pool-prefixes) - Optional List<br>IPv4 Prefix List. List of IPv4 prefixes that represent an endpoint
+
+#### Origin Servers Public IP
+
+A [`public_ip`](#origin-servers-public-ip) block (within [`origin_servers`](#origin-servers)) supports the following:
+
+<a id="origin-servers-public-ip-ip"></a>&#x2022; [`ip`](#origin-servers-public-ip-ip) - Optional String<br>Public IPv4. Public IPv4 address
+
+#### Origin Servers Public Name
+
+A [`public_name`](#origin-servers-public-name) block (within [`origin_servers`](#origin-servers)) supports the following:
+
+<a id="origin-servers-public-name-dns-name"></a>&#x2022; [`dns_name`](#origin-servers-public-name-dns-name) - Optional String<br>DNS Name. DNS Name
+
+<a id="origin-servers-public-name-refresh-interval"></a>&#x2022; [`refresh_interval`](#origin-servers-public-name-refresh-interval) - Optional Number<br>DNS Refresh Interval. Interval for DNS refresh in seconds. Max value is 7 days as per `HTTPS://datatracker.ietf.org/doc/HTML/rfc8767`
+
+#### Origin Servers Vn Private IP
+
+A [`vn_private_ip`](#origin-servers-vn-private-ip) block (within [`origin_servers`](#origin-servers)) supports the following:
+
+<a id="origin-servers-vn-private-ip-ip"></a>&#x2022; [`ip`](#origin-servers-vn-private-ip-ip) - Optional String<br>IPv4. IPv4 address
+
+<a id="origin-servers-vn-private-ip-virtual-network"></a>&#x2022; [`virtual_network`](#origin-servers-vn-private-ip-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](#origin-servers-vn-private-ip-virtual-network) below.
+
+#### Origin Servers Vn Private IP Virtual Network
+
+A [`virtual_network`](#origin-servers-vn-private-ip-virtual-network) block (within [`origin_servers.vn_private_ip`](#origin-servers-vn-private-ip)) supports the following:
+
+<a id="origin-servers-vn-private-ip-virtual-network-name"></a>&#x2022; [`name`](#origin-servers-vn-private-ip-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="origin-servers-vn-private-ip-virtual-network-namespace"></a>&#x2022; [`namespace`](#origin-servers-vn-private-ip-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="origin-servers-vn-private-ip-virtual-network-tenant"></a>&#x2022; [`tenant`](#origin-servers-vn-private-ip-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
+
+#### Origin Servers Vn Private Name
+
+A [`vn_private_name`](#origin-servers-vn-private-name) block (within [`origin_servers`](#origin-servers)) supports the following:
+
+<a id="origin-servers-vn-private-name-dns-name"></a>&#x2022; [`dns_name`](#origin-servers-vn-private-name-dns-name) - Optional String<br>DNS Name. DNS Name
+
+<a id="origin-servers-vn-private-name-private-network"></a>&#x2022; [`private_network`](#origin-servers-vn-private-name-private-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 [Private Network](#origin-servers-vn-private-name-private-network) below.
+
+#### Origin Servers Vn Private Name Private Network
+
+A [`private_network`](#origin-servers-vn-private-name-private-network) block (within [`origin_servers.vn_private_name`](#origin-servers-vn-private-name)) supports the following:
+
+<a id="origin-servers-vn-private-name-private-network-name"></a>&#x2022; [`name`](#origin-servers-vn-private-name-private-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="origin-servers-vn-private-name-private-network-namespace"></a>&#x2022; [`namespace`](#origin-servers-vn-private-name-private-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="origin-servers-vn-private-name-private-network-tenant"></a>&#x2022; [`tenant`](#origin-servers-vn-private-name-private-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
+
+#### 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
+
+#### Upstream Conn Pool Reuse Type
+
+An [`upstream_conn_pool_reuse_type`](#upstream-conn-pool-reuse-type) block supports the following:
+
+<a id="upstream-conn-pool-reuse-type-disable-conn-pool-reuse"></a>&#x2022; [`disable_conn_pool_reuse`](#upstream-conn-pool-reuse-type-disable-conn-pool-reuse) - Optional Block<br>Enable this option
+
+<a id="upstream-conn-pool-reuse-type-enable-conn-pool-reuse"></a>&#x2022; [`enable_conn_pool_reuse`](#upstream-conn-pool-reuse-type-enable-conn-pool-reuse) - Optional Block<br>Enable this option
+
+#### Use TLS
+
+An [`use_tls`](#use-tls) block supports the following:
+
+<a id="use-tls-default-session-key-caching"></a>&#x2022; [`default_session_key_caching`](#use-tls-default-session-key-caching) - Optional Block<br>Enable this option
+
+<a id="use-tls-disable-session-key-caching"></a>&#x2022; [`disable_session_key_caching`](#use-tls-disable-session-key-caching) - Optional Block<br>Enable this option
+
+<a id="use-tls-disable-sni"></a>&#x2022; [`disable_sni`](#use-tls-disable-sni) - Optional Block<br>Enable this option
+
+<a id="use-tls-max-session-keys"></a>&#x2022; [`max_session_keys`](#use-tls-max-session-keys) - Optional Number<br>Max Session Keys Cached. Number of session keys that are cached
+
+<a id="use-tls-no-mtls"></a>&#x2022; [`no_mtls`](#use-tls-no-mtls) - Optional Block<br>Enable this option
+
+<a id="use-tls-skip-server-verification"></a>&#x2022; [`skip_server_verification`](#use-tls-skip-server-verification) - Optional Block<br>Enable this option
+
+<a id="use-tls-sni"></a>&#x2022; [`sni`](#use-tls-sni) - Optional String<br>SNI Value. SNI value to be used
+
+<a id="use-tls-tls-config"></a>&#x2022; [`tls_config`](#use-tls-tls-config) - Optional Block<br>TLS Config. This defines various options to configure TLS configuration parameters<br>See [TLS Config](#use-tls-tls-config) below.
+
+<a id="use-tls-use-host-header-as-sni"></a>&#x2022; [`use_host_header_as_sni`](#use-tls-use-host-header-as-sni) - Optional Block<br>Enable this option
+
+<a id="use-tls-use-mtls"></a>&#x2022; [`use_mtls`](#use-tls-use-mtls) - Optional Block<br>mTLS Certificate. mTLS Client Certificate<br>See [Use mTLS](#use-tls-use-mtls) below.
+
+<a id="use-tls-use-mtls-obj"></a>&#x2022; [`use_mtls_obj`](#use-tls-use-mtls-obj) - 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 [Use mTLS Obj](#use-tls-use-mtls-obj) below.
+
+<a id="use-tls-use-server-verification"></a>&#x2022; [`use_server_verification`](#use-tls-use-server-verification) - Optional Block<br>TLS Validation Context for Origin Servers. Upstream TLS Validation Context<br>See [Use Server Verification](#use-tls-use-server-verification) below.
+
+<a id="use-tls-volterra-trusted-ca"></a>&#x2022; [`volterra_trusted_ca`](#use-tls-volterra-trusted-ca) - Optional Block<br>Enable this option
+
+#### Use TLS TLS Config
+
+A [`tls_config`](#use-tls-tls-config) block (within [`use_tls`](#use-tls)) supports the following:
+
+<a id="use-tls-tls-config-custom-security"></a>&#x2022; [`custom_security`](#use-tls-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](#use-tls-tls-config-custom-security) below.
+
+<a id="use-tls-tls-config-default-security"></a>&#x2022; [`default_security`](#use-tls-tls-config-default-security) - Optional Block<br>Enable this option
+
+<a id="use-tls-tls-config-low-security"></a>&#x2022; [`low_security`](#use-tls-tls-config-low-security) - Optional Block<br>Enable this option
+
+<a id="use-tls-tls-config-medium-security"></a>&#x2022; [`medium_security`](#use-tls-tls-config-medium-security) - Optional Block<br>Enable this option
+
+#### Use TLS TLS Config Custom Security
+
+A [`custom_security`](#use-tls-tls-config-custom-security) block (within [`use_tls.tls_config`](#use-tls-tls-config)) supports the following:
+
+<a id="use-tls-tls-config-custom-security-cipher-suites"></a>&#x2022; [`cipher_suites`](#use-tls-tls-config-custom-security-cipher-suites) - Optional List<br>Cipher Suites. The TLS listener will only support the specified cipher list
+
+<a id="use-tls-tls-config-custom-security-max-version"></a>&#x2022; [`max_version`](#use-tls-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="use-tls-tls-config-custom-security-min-version"></a>&#x2022; [`min_version`](#use-tls-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
+
+#### Use TLS Use mTLS
+
+An [`use_mtls`](#use-tls-use-mtls) block (within [`use_tls`](#use-tls)) supports the following:
+
+<a id="use-tls-use-mtls-tls-certificates"></a>&#x2022; [`tls_certificates`](#use-tls-use-mtls-tls-certificates) - Optional Block<br>mTLS Client Certificate. mTLS Client Certificate<br>See [TLS Certificates](#use-tls-use-mtls-tls-certificates) below.
+
+#### Use TLS Use mTLS TLS Certificates
+
+A [`tls_certificates`](#use-tls-use-mtls-tls-certificates) block (within [`use_tls.use_mtls`](#use-tls-use-mtls)) supports the following:
+
+<a id="use-tls-use-mtls-tls-certificates-certificate-url"></a>&#x2022; [`certificate_url`](#use-tls-use-mtls-tls-certificates-certificate-url) - Optional String<br>Certificate. TLS certificate. Certificate or certificate chain in PEM format including the PEM headers
+
+<a id="use-tls-use-mtls-tls-certificates-custom-hash-algorithms"></a>&#x2022; [`custom_hash_algorithms`](#use-tls-use-mtls-tls-certificates-custom-hash-algorithms) - Optional Block<br>Hash Algorithms. Specifies the hash algorithms to be used<br>See [Custom Hash Algorithms](#use-tls-use-mtls-tls-certificates-custom-hash-algorithms) below.
+
+<a id="use-tls-use-mtls-tls-certificates-description-spec"></a>&#x2022; [`description_spec`](#use-tls-use-mtls-tls-certificates-description-spec) - Optional String<br>Description. Description for the certificate
+
+<a id="use-tls-use-mtls-tls-certificates-disable-ocsp-stapling"></a>&#x2022; [`disable_ocsp_stapling`](#use-tls-use-mtls-tls-certificates-disable-ocsp-stapling) - Optional Block<br>Enable this option
+
+<a id="use-tls-use-mtls-tls-certificates-private-key"></a>&#x2022; [`private_key`](#use-tls-use-mtls-tls-certificates-private-key) - Optional Block<br>Secret. SecretType is used in an object to indicate a sensitive/confidential field<br>See [Private Key](#use-tls-use-mtls-tls-certificates-private-key) below.
+
+<a id="use-tls-use-mtls-tls-certificates-use-system-defaults"></a>&#x2022; [`use_system_defaults`](#use-tls-use-mtls-tls-certificates-use-system-defaults) - Optional Block<br>Enable this option
+
+#### Use TLS Use mTLS TLS Certificates Custom Hash Algorithms
+
+A [`custom_hash_algorithms`](#use-tls-use-mtls-tls-certificates-custom-hash-algorithms) block (within [`use_tls.use_mtls.tls_certificates`](#use-tls-use-mtls-tls-certificates)) supports the following:
+
+<a id="use-tls-use-mtls-tls-certificates-custom-hash-algorithms-hash-algorithms"></a>&#x2022; [`hash_algorithms`](#use-tls-use-mtls-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
+
+#### Use TLS Use mTLS TLS Certificates Private Key
+
+A [`private_key`](#use-tls-use-mtls-tls-certificates-private-key) block (within [`use_tls.use_mtls.tls_certificates`](#use-tls-use-mtls-tls-certificates)) supports the following:
+
+<a id="use-tls-use-mtls-tls-certificates-private-key-blindfold-secret-info"></a>&#x2022; [`blindfold_secret_info`](#use-tls-use-mtls-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](#use-tls-use-mtls-tls-certificates-private-key-blindfold-secret-info) below.
+
+<a id="use-tls-use-mtls-tls-certificates-private-key-clear-secret-info"></a>&#x2022; [`clear_secret_info`](#use-tls-use-mtls-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](#use-tls-use-mtls-tls-certificates-private-key-clear-secret-info) below.
+
+#### Use TLS Use mTLS TLS Certificates Private Key Blindfold Secret Info
+
+A [`blindfold_secret_info`](#use-tls-use-mtls-tls-certificates-private-key-blindfold-secret-info) block (within [`use_tls.use_mtls.tls_certificates.private_key`](#use-tls-use-mtls-tls-certificates-private-key)) supports the following:
+
+<a id="use-tls-use-mtls-tls-certificates-private-key-blindfold-secret-info-decryption-provider"></a>&#x2022; [`decryption_provider`](#use-tls-use-mtls-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="use-tls-use-mtls-tls-certificates-private-key-blindfold-secret-info-location"></a>&#x2022; [`location`](#use-tls-use-mtls-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="use-tls-use-mtls-tls-certificates-private-key-blindfold-secret-info-store-provider"></a>&#x2022; [`store_provider`](#use-tls-use-mtls-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:///
+
+#### Use TLS Use mTLS TLS Certificates Private Key Clear Secret Info
+
+A [`clear_secret_info`](#use-tls-use-mtls-tls-certificates-private-key-clear-secret-info) block (within [`use_tls.use_mtls.tls_certificates.private_key`](#use-tls-use-mtls-tls-certificates-private-key)) supports the following:
+
+<a id="use-tls-use-mtls-tls-certificates-private-key-clear-secret-info-provider-ref"></a>&#x2022; [`provider_ref`](#use-tls-use-mtls-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="use-tls-use-mtls-tls-certificates-private-key-clear-secret-info-url"></a>&#x2022; [`url`](#use-tls-use-mtls-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
+
+#### Use TLS Use mTLS Obj
+
+An [`use_mtls_obj`](#use-tls-use-mtls-obj) block (within [`use_tls`](#use-tls)) supports the following:
+
+<a id="use-tls-use-mtls-obj-name"></a>&#x2022; [`name`](#use-tls-use-mtls-obj-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="use-tls-use-mtls-obj-namespace"></a>&#x2022; [`namespace`](#use-tls-use-mtls-obj-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="use-tls-use-mtls-obj-tenant"></a>&#x2022; [`tenant`](#use-tls-use-mtls-obj-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
+
+#### Use TLS Use Server Verification
+
+An [`use_server_verification`](#use-tls-use-server-verification) block (within [`use_tls`](#use-tls)) supports the following:
+
+<a id="use-tls-use-server-verification-trusted-ca"></a>&#x2022; [`trusted_ca`](#use-tls-use-server-verification-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](#use-tls-use-server-verification-trusted-ca) below.
+
+<a id="use-tls-use-server-verification-trusted-ca-url"></a>&#x2022; [`trusted_ca_url`](#use-tls-use-server-verification-trusted-ca-url) - Optional String<br>Inline Root CA Certificate (legacy). Upload a Root CA Certificate specifically for this Origin Pool for verification of server's certificate
+
+#### Use TLS Use Server Verification Trusted CA
+
+A [`trusted_ca`](#use-tls-use-server-verification-trusted-ca) block (within [`use_tls.use_server_verification`](#use-tls-use-server-verification)) supports the following:
+
+<a id="use-tls-use-server-verification-trusted-ca-name"></a>&#x2022; [`name`](#use-tls-use-server-verification-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="use-tls-use-server-verification-trusted-ca-namespace"></a>&#x2022; [`namespace`](#use-tls-use-server-verification-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="use-tls-use-server-verification-trusted-ca-tenant"></a>&#x2022; [`tenant`](#use-tls-use-server-verification-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
+
+## Import
+
+Import is supported using the following syntax:
+
+```shell
+# Import using namespace/name format
+terraform import f5xc_origin_pool.example system/example
+```