metio · github-actions · Apr 25, 2024 · Apr 24, 2024 · Apr 25, 2024 · Apr 25, 2024
diff --git a/docs/data-sources/app_kiegroup_org_kogito_infra_v1beta1_manifest.md b/docs/data-sources/app_kiegroup_org_kogito_infra_v1beta1_manifest.md
@@ -3,7 +3,7 @@
 page_title: "k8s_app_kiegroup_org_kogito_infra_v1beta1_manifest Data Source - terraform-provider-k8s"
 subcategory: "app.kiegroup.org"
 description: |-
-  KogitoInfra is the resource to bind a Custom Resource (CR) not managed by Kogito Operator to a given deployed Kogito service.  It holds the reference of a CR managed by another operator such as Strimzi. For example: one can create a Kafka CR via Strimzi and link this resource using KogitoInfra to a given Kogito service (custom or supporting, such as Data Index).  Please refer to the Kogito Operator documentation () for more information.
+  KogitoInfra is the resource to bind a Custom Resource (CR) not managed by Kogito Operator to a given deployed Kogito service.  It holds the reference of a CR managed by another operator such as Strimzi. For example: one can create a Kafka CR via Strimzi and link this resource using KogitoInfra to a given Kogito service (custom or supporting, such as Data Index).  Please refer to the Kogito Operator documentation (https://docs.jboss.org/kogito/release/latest/html_single/) for more information.
 ---
 
 # k8s_app_kiegroup_org_kogito_infra_v1beta1_manifest (Data Source)

diff --git a/docs/data-sources/app_terraform_io_module_v1alpha2_manifest.md b/docs/data-sources/app_terraform_io_module_v1alpha2_manifest.md
@@ -3,7 +3,7 @@
 page_title: "k8s_app_terraform_io_module_v1alpha2_manifest Data Source - terraform-provider-k8s"
 subcategory: "app.terraform.io"
 description: |-
-  Module is the Schema for the modules APIModule implements the API-driven Run WorkflowMore information:  -
+  Module is the Schema for the modules APIModule implements the API-driven Run WorkflowMore information:  - https://developer.hashicorp.com/terraform/cloud-docs/run/api
 ---
 
 # k8s_app_terraform_io_module_v1alpha2_manifest (Data Source)

diff --git a/docs/data-sources/couchbase_com_couchbase_migration_replication_v2_manifest.md b/docs/data-sources/couchbase_com_couchbase_migration_replication_v2_manifest.md
@@ -3,7 +3,7 @@
 page_title: "k8s_couchbase_com_couchbase_migration_replication_v2_manifest Data Source - terraform-provider-k8s"
 subcategory: "couchbase.com"
 description: |-
-  The CouchbaseScopeMigration resource represents the use of the special migration mapping within XDCR to take a filtered list from the default scope and collection of the source bucket, replicate it to named scopes and collections within the target bucket. The bucket-to-bucket replication cannot duplicate any used by the CouchbaseReplication resource, as these two types of replication are mutually exclusive between buckets.
+  The CouchbaseScopeMigration resource represents the use of the special migration mapping within XDCR to take a filtered list from the default scope and collection of the source bucket, replicate it to named scopes and collections within the target bucket. The bucket-to-bucket replication cannot duplicate any used by the CouchbaseReplication resource, as these two types of replication are mutually exclusive between buckets. https://docs.couchbase.com/server/current/learn/clusters-and-availability/xdcr-with-scopes-and-collections.html#migration
 ---
 
 # k8s_couchbase_com_couchbase_migration_replication_v2_manifest (Data Source)

diff --git a/docs/data-sources/gateway_networking_k8s_io_grpc_route_v1_manifest.md b/docs/data-sources/gateway_networking_k8s_io_grpc_route_v1_manifest.md
@@ -3,7 +3,7 @@
 page_title: "k8s_gateway_networking_k8s_io_grpc_route_v1_manifest Data Source - terraform-provider-k8s"
 subcategory: "gateway.networking.k8s.io"
 description: |-
-  GRPCRoute provides a way to route gRPC requests. This includes the capabilityto match requests by hostname, gRPC service, gRPC method, or HTTP/2 header.Filters can be used to specify additional processing steps. Backends specifywhere matching requests will be routed.GRPCRoute falls under extended support within the Gateway API. Within thefollowing specification, the word 'MUST' indicates that an implementationsupporting GRPCRoute must conform to the indicated requirement, but animplementation not supporting this route type need not follow the requirementunless explicitly indicated.Implementations supporting 'GRPCRoute' with the 'HTTPS' 'ProtocolType' MUSTaccept HTTP/2 connections without an initial upgrade from HTTP/1.1, i.e. viaALPN. If the implementation does not support this, then it MUST set the'Accepted' condition to 'False' for the affected listener with a reason of'UnsupportedProtocol'.  Implementations MAY also accept HTTP/2 connectionswith an upgrade from HTTP/1.Implementations supporting 'GRPCRoute' with the 'HTTP' 'ProtocolType' MUSTsupport HTTP/2 over cleartext TCP (h2c,https://www.rfc-editor.org/rfc/rfc7540#section-3.1) without an initialupgrade from HTTP/1.1, i.e. with prior knowledge(. If the implementationdoes not support this, then it MUST set the 'Accepted' condition to 'False'for the affected listener with a reason of 'UnsupportedProtocol'.Implementations MAY also accept HTTP/2 connections with an upgrade fromHTTP/1, i.e. without prior knowledge.
+  GRPCRoute provides a way to route gRPC requests. This includes the capabilityto match requests by hostname, gRPC service, gRPC method, or HTTP/2 header.Filters can be used to specify additional processing steps. Backends specifywhere matching requests will be routed.GRPCRoute falls under extended support within the Gateway API. Within thefollowing specification, the word 'MUST' indicates that an implementationsupporting GRPCRoute must conform to the indicated requirement, but animplementation not supporting this route type need not follow the requirementunless explicitly indicated.Implementations supporting 'GRPCRoute' with the 'HTTPS' 'ProtocolType' MUSTaccept HTTP/2 connections without an initial upgrade from HTTP/1.1, i.e. viaALPN. If the implementation does not support this, then it MUST set the'Accepted' condition to 'False' for the affected listener with a reason of'UnsupportedProtocol'.  Implementations MAY also accept HTTP/2 connectionswith an upgrade from HTTP/1.Implementations supporting 'GRPCRoute' with the 'HTTP' 'ProtocolType' MUSTsupport HTTP/2 over cleartext TCP (h2c,https://www.rfc-editor.org/rfc/rfc7540#section-3.1) without an initialupgrade from HTTP/1.1, i.e. with prior knowledge(https://www.rfc-editor.org/rfc/rfc7540#section-3.4). If the implementationdoes not support this, then it MUST set the 'Accepted' condition to 'False'for the affected listener with a reason of 'UnsupportedProtocol'.Implementations MAY also accept HTTP/2 connections with an upgrade fromHTTP/1, i.e. without prior knowledge.
 ---
 
 # k8s_gateway_networking_k8s_io_grpc_route_v1_manifest (Data Source)

diff --git a/docs/data-sources/gateway_networking_k8s_io_grpc_route_v1alpha2_manifest.md b/docs/data-sources/gateway_networking_k8s_io_grpc_route_v1alpha2_manifest.md
@@ -3,7 +3,7 @@
 page_title: "k8s_gateway_networking_k8s_io_grpc_route_v1alpha2_manifest Data Source - terraform-provider-k8s"
 subcategory: "gateway.networking.k8s.io"
 description: |-
-  GRPCRoute provides a way to route gRPC requests. This includes the capabilityto match requests by hostname, gRPC service, gRPC method, or HTTP/2 header.Filters can be used to specify additional processing steps. Backends specifywhere matching requests will be routed.GRPCRoute falls under extended support within the Gateway API. Within thefollowing specification, the word 'MUST' indicates that an implementationsupporting GRPCRoute must conform to the indicated requirement, but animplementation not supporting this route type need not follow the requirementunless explicitly indicated.Implementations supporting 'GRPCRoute' with the 'HTTPS' 'ProtocolType' MUSTaccept HTTP/2 connections without an initial upgrade from HTTP/1.1, i.e. viaALPN. If the implementation does not support this, then it MUST set the'Accepted' condition to 'False' for the affected listener with a reason of'UnsupportedProtocol'.  Implementations MAY also accept HTTP/2 connectionswith an upgrade from HTTP/1.Implementations supporting 'GRPCRoute' with the 'HTTP' 'ProtocolType' MUSTsupport HTTP/2 over cleartext TCP (h2c,https://www.rfc-editor.org/rfc/rfc7540#section-3.1) without an initialupgrade from HTTP/1.1, i.e. with prior knowledge(. If the implementationdoes not support this, then it MUST set the 'Accepted' condition to 'False'for the affected listener with a reason of 'UnsupportedProtocol'.Implementations MAY also accept HTTP/2 connections with an upgrade fromHTTP/1, i.e. without prior knowledge.
+  GRPCRoute provides a way to route gRPC requests. This includes the capabilityto match requests by hostname, gRPC service, gRPC method, or HTTP/2 header.Filters can be used to specify additional processing steps. Backends specifywhere matching requests will be routed.GRPCRoute falls under extended support within the Gateway API. Within thefollowing specification, the word 'MUST' indicates that an implementationsupporting GRPCRoute must conform to the indicated requirement, but animplementation not supporting this route type need not follow the requirementunless explicitly indicated.Implementations supporting 'GRPCRoute' with the 'HTTPS' 'ProtocolType' MUSTaccept HTTP/2 connections without an initial upgrade from HTTP/1.1, i.e. viaALPN. If the implementation does not support this, then it MUST set the'Accepted' condition to 'False' for the affected listener with a reason of'UnsupportedProtocol'.  Implementations MAY also accept HTTP/2 connectionswith an upgrade from HTTP/1.Implementations supporting 'GRPCRoute' with the 'HTTP' 'ProtocolType' MUSTsupport HTTP/2 over cleartext TCP (h2c,https://www.rfc-editor.org/rfc/rfc7540#section-3.1) without an initialupgrade from HTTP/1.1, i.e. with prior knowledge(https://www.rfc-editor.org/rfc/rfc7540#section-3.4). If the implementationdoes not support this, then it MUST set the 'Accepted' condition to 'False'for the affected listener with a reason of 'UnsupportedProtocol'.Implementations MAY also accept HTTP/2 connections with an upgrade fromHTTP/1, i.e. without prior knowledge.
 ---
 
 # k8s_gateway_networking_k8s_io_grpc_route_v1alpha2_manifest (Data Source)

diff --git a/docs/data-sources/getambassador_io_module_v1_manifest.md b/docs/data-sources/getambassador_io_module_v1_manifest.md
@@ -3,7 +3,7 @@
 page_title: "k8s_getambassador_io_module_v1_manifest Data Source - terraform-provider-k8s"
 subcategory: "getambassador.io"
 description: |-
-  A Module defines system-wide configuration.  The type of module is controlled by the .metadata.name; valid names are 'ambassador' or 'tls'.
+  A Module defines system-wide configuration.  The type of module is controlled by the .metadata.name; valid names are 'ambassador' or 'tls'.  https://www.getambassador.io/docs/edge-stack/latest/topics/running/ambassador/#the-ambassador-module https://www.getambassador.io/docs/edge-stack/latest/topics/running/tls/#tls-module-deprecated
 ---
 
 # k8s_getambassador_io_module_v1_manifest (Data Source)

diff --git a/docs/data-sources/getambassador_io_module_v2_manifest.md b/docs/data-sources/getambassador_io_module_v2_manifest.md
@@ -3,7 +3,7 @@
 page_title: "k8s_getambassador_io_module_v2_manifest Data Source - terraform-provider-k8s"
 subcategory: "getambassador.io"
 description: |-
-  A Module defines system-wide configuration.  The type of module is controlled by the .metadata.name; valid names are 'ambassador' or 'tls'.
+  A Module defines system-wide configuration.  The type of module is controlled by the .metadata.name; valid names are 'ambassador' or 'tls'.  https://www.getambassador.io/docs/edge-stack/latest/topics/running/ambassador/#the-ambassador-module https://www.getambassador.io/docs/edge-stack/latest/topics/running/tls/#tls-module-deprecated
 ---
 
 # k8s_getambassador_io_module_v2_manifest (Data Source)

diff --git a/docs/data-sources/getambassador_io_module_v3alpha1_manifest.md b/docs/data-sources/getambassador_io_module_v3alpha1_manifest.md
@@ -3,7 +3,7 @@
 page_title: "k8s_getambassador_io_module_v3alpha1_manifest Data Source - terraform-provider-k8s"
 subcategory: "getambassador.io"
 description: |-
-  A Module defines system-wide configuration.  The type of module is controlled by the .metadata.name; valid names are 'ambassador' or 'tls'.
+  A Module defines system-wide configuration.  The type of module is controlled by the .metadata.name; valid names are 'ambassador' or 'tls'.  https://www.getambassador.io/docs/edge-stack/latest/topics/running/ambassador/#the-ambassador-module https://www.getambassador.io/docs/edge-stack/latest/topics/running/tls/#tls-module-deprecated
 ---
 
 # k8s_getambassador_io_module_v3alpha1_manifest (Data Source)

diff --git a/docs/data-sources/hnc_x_k8s_io_hnc_configuration_v1alpha2_manifest.md b/docs/data-sources/hnc_x_k8s_io_hnc_configuration_v1alpha2_manifest.md
@@ -3,7 +3,7 @@
 page_title: "k8s_hnc_x_k8s_io_hnc_configuration_v1alpha2_manifest Data Source - terraform-provider-k8s"
 subcategory: "hnc.x-k8s.io"
 description: |-
-  HNCConfiguration is a cluster-wide configuration for HNC as a whole. See details in
+  HNCConfiguration is a cluster-wide configuration for HNC as a whole. See details in http://bit.ly/hnc-type-configuration
 ---
 
 # k8s_hnc_x_k8s_io_hnc_configuration_v1alpha2_manifest (Data Source)

diff --git a/docs/data-sources/hnc_x_k8s_io_subnamespace_anchor_v1alpha2_manifest.md b/docs/data-sources/hnc_x_k8s_io_subnamespace_anchor_v1alpha2_manifest.md
@@ -3,7 +3,7 @@
 page_title: "k8s_hnc_x_k8s_io_subnamespace_anchor_v1alpha2_manifest Data Source - terraform-provider-k8s"
 subcategory: "hnc.x-k8s.io"
 description: |-
-  SubnamespaceAnchor is the Schema for the subnamespace API. See details at .
+  SubnamespaceAnchor is the Schema for the subnamespace API. See details at http://bit.ly/hnc-self-serve-ux.
 ---
 
 # k8s_hnc_x_k8s_io_subnamespace_anchor_v1alpha2_manifest (Data Source)

diff --git a/docs/data-sources/kyverno_io_policy_v1_manifest.md b/docs/data-sources/kyverno_io_policy_v1_manifest.md
@@ -3,7 +3,7 @@
 page_title: "k8s_kyverno_io_policy_v1_manifest Data Source - terraform-provider-k8s"
 subcategory: "kyverno.io"
 description: |-
-  Policy declares validation, mutation, and generation behaviors for matching resources.See:  for more information.
+  Policy declares validation, mutation, and generation behaviors for matching resources.See: https://kyverno.io/docs/writing-policies/ for more information.
 ---
 
 # k8s_kyverno_io_policy_v1_manifest (Data Source)

diff --git a/docs/data-sources/kyverno_io_policy_v2beta1_manifest.md b/docs/data-sources/kyverno_io_policy_v2beta1_manifest.md
@@ -3,7 +3,7 @@
 page_title: "k8s_kyverno_io_policy_v2beta1_manifest Data Source - terraform-provider-k8s"
 subcategory: "kyverno.io"
 description: |-
-  Policy declares validation, mutation, and generation behaviors for matching resources.See:  for more information.
+  Policy declares validation, mutation, and generation behaviors for matching resources.See: https://kyverno.io/docs/writing-policies/ for more information.
 ---
 
 # k8s_kyverno_io_policy_v2beta1_manifest (Data Source)

diff --git a/docs/data-sources/persistent_volume_v1_manifest.md b/docs/data-sources/persistent_volume_v1_manifest.md
@@ -3,7 +3,7 @@
 page_title: "k8s_persistent_volume_v1_manifest Data Source - terraform-provider-k8s"
 subcategory: "core"
 description: |-
-  PersistentVolume (PV) is a storage resource provisioned by an administrator. It is analogous to a node. More info:
+  PersistentVolume (PV) is a storage resource provisioned by an administrator. It is analogous to a node. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes
 ---
 
 # k8s_persistent_volume_v1_manifest (Data Source)

diff --git a/...sources/security_profiles_operator_x_k8s_io_seccomp_profile_v1beta1_manifest.md b/...sources/security_profiles_operator_x_k8s_io_seccomp_profile_v1beta1_manifest.md
@@ -3,7 +3,7 @@
 page_title: "k8s_security_profiles_operator_x_k8s_io_seccomp_profile_v1beta1_manifest Data Source - terraform-provider-k8s"
 subcategory: "security-profiles-operator.x-k8s.io"
 description: |-
-  SeccompProfile is a cluster level specification for a seccomp profile.See
+  SeccompProfile is a cluster level specification for a seccomp profile.See https://github.com/opencontainers/runtime-spec/blob/master/config-linux.md#seccomp
 ---
 
 # k8s_security_profiles_operator_x_k8s_io_seccomp_profile_v1beta1_manifest (Data Source)

diff --git a/docs/data-sources/stunner_l7mp_io_static_service_v1_manifest.md b/docs/data-sources/stunner_l7mp_io_static_service_v1_manifest.md
@@ -3,7 +3,7 @@
 page_title: "k8s_stunner_l7mp_io_static_service_v1_manifest Data Source - terraform-provider-k8s"
 subcategory: "stunner.l7mp.io"
 description: |-
-  StaticService is a set of static IP address prefixes STUNner allows access to via a UDPRoute (or TCPRoute in the future). In contrast to Kubernetes Services, StaticServices expose all ports on the given IPs. See also .
+  StaticService is a set of static IP address prefixes STUNner allows access to via a UDPRoute (or TCPRoute in the future). In contrast to Kubernetes Services, StaticServices expose all ports on the given IPs. See also https://github.com/kubernetes/enhancements/pull/2611.
 ---
 
 # k8s_stunner_l7mp_io_static_service_v1_manifest (Data Source)

diff --git a/docs/data-sources/tinkerbell_org_template_v1alpha2_manifest.md b/docs/data-sources/tinkerbell_org_template_v1alpha2_manifest.md
@@ -3,7 +3,7 @@
 page_title: "k8s_tinkerbell_org_template_v1alpha2_manifest Data Source - terraform-provider-k8s"
 subcategory: "tinkerbell.org"
 description: |-
-  Template defines a set of actions to be run on a target machine. The template is renderedprior to execution where it is exposed to Hardware and user defined data. Most fields within theTemplateSpec may contain templates values excluding .TemplateSpec.Actions[].Name.See  for more details.
+  Template defines a set of actions to be run on a target machine. The template is renderedprior to execution where it is exposed to Hardware and user defined data. Most fields within theTemplateSpec may contain templates values excluding .TemplateSpec.Actions[].Name.See https://pkg.go.dev/text/template for more details.
 ---
 
 # k8s_tinkerbell_org_template_v1alpha2_manifest (Data Source)

diff --git a/docs/data-sources/traefik_io_middleware_tcp_v1alpha1_manifest.md b/docs/data-sources/traefik_io_middleware_tcp_v1alpha1_manifest.md
@@ -3,7 +3,7 @@
 page_title: "k8s_traefik_io_middleware_tcp_v1alpha1_manifest Data Source - terraform-provider-k8s"
 subcategory: "traefik.io"
 description: |-
-  MiddlewareTCP is the CRD implementation of a Traefik TCP middleware.More info:
+  MiddlewareTCP is the CRD implementation of a Traefik TCP middleware.More info: https://doc.traefik.io/traefik/v3.0/middlewares/overview/
 ---
 
 # k8s_traefik_io_middleware_tcp_v1alpha1_manifest (Data Source)

diff --git a/docs/data-sources/traefik_io_middleware_v1alpha1_manifest.md b/docs/data-sources/traefik_io_middleware_v1alpha1_manifest.md
@@ -3,7 +3,7 @@
 page_title: "k8s_traefik_io_middleware_v1alpha1_manifest Data Source - terraform-provider-k8s"
 subcategory: "traefik.io"
 description: |-
-  Middleware is the CRD implementation of a Traefik Middleware.More info:
+  Middleware is the CRD implementation of a Traefik Middleware.More info: https://doc.traefik.io/traefik/v3.0/middlewares/http/overview/
 ---
 
 # k8s_traefik_io_middleware_v1alpha1_manifest (Data Source)

diff --git a/docs/data-sources/traefik_io_servers_transport_tcp_v1alpha1_manifest.md b/docs/data-sources/traefik_io_servers_transport_tcp_v1alpha1_manifest.md
@@ -3,7 +3,7 @@
 page_title: "k8s_traefik_io_servers_transport_tcp_v1alpha1_manifest Data Source - terraform-provider-k8s"
 subcategory: "traefik.io"
 description: |-
-  ServersTransportTCP is the CRD implementation of a TCPServersTransport.If no tcpServersTransport is specified, a default one named default@internal will be used.The default@internal tcpServersTransport can be configured in the static configuration.More info:
+  ServersTransportTCP is the CRD implementation of a TCPServersTransport.If no tcpServersTransport is specified, a default one named default@internal will be used.The default@internal tcpServersTransport can be configured in the static configuration.More info: https://doc.traefik.io/traefik/v3.0/routing/services/#serverstransport_3
 ---
 
 # k8s_traefik_io_servers_transport_tcp_v1alpha1_manifest (Data Source)

diff --git a/docs/data-sources/traefik_io_servers_transport_v1alpha1_manifest.md b/docs/data-sources/traefik_io_servers_transport_v1alpha1_manifest.md
@@ -3,7 +3,7 @@
 page_title: "k8s_traefik_io_servers_transport_v1alpha1_manifest Data Source - terraform-provider-k8s"
 subcategory: "traefik.io"
 description: |-
-  ServersTransport is the CRD implementation of a ServersTransport.If no serversTransport is specified, the default@internal will be used.The default@internal serversTransport is created from the static configuration.More info:
+  ServersTransport is the CRD implementation of a ServersTransport.If no serversTransport is specified, the default@internal will be used.The default@internal serversTransport is created from the static configuration.More info: https://doc.traefik.io/traefik/v3.0/routing/services/#serverstransport_1
 ---
 
 # k8s_traefik_io_servers_transport_v1alpha1_manifest (Data Source)

diff --git a/docs/data-sources/traefik_io_tls_option_v1alpha1_manifest.md b/docs/data-sources/traefik_io_tls_option_v1alpha1_manifest.md
@@ -3,7 +3,7 @@
 page_title: "k8s_traefik_io_tls_option_v1alpha1_manifest Data Source - terraform-provider-k8s"
 subcategory: "traefik.io"
 description: |-
-  TLSOption is the CRD implementation of a Traefik TLS Option, allowing to configure some parameters of the TLS connection.More info:
+  TLSOption is the CRD implementation of a Traefik TLS Option, allowing to configure some parameters of the TLS connection.More info: https://doc.traefik.io/traefik/v3.0/https/tls/#tls-options
 ---
 
 # k8s_traefik_io_tls_option_v1alpha1_manifest (Data Source)

diff --git a/docs/data-sources/traefik_io_tls_store_v1alpha1_manifest.md b/docs/data-sources/traefik_io_tls_store_v1alpha1_manifest.md
@@ -3,7 +3,7 @@
 page_title: "k8s_traefik_io_tls_store_v1alpha1_manifest Data Source - terraform-provider-k8s"
 subcategory: "traefik.io"
 description: |-
-  TLSStore is the CRD implementation of a Traefik TLS Store.For the time being, only the TLSStore named default is supported.This means that you cannot have two stores that are named default in different Kubernetes namespaces.More info:
+  TLSStore is the CRD implementation of a Traefik TLS Store.For the time being, only the TLSStore named default is supported.This means that you cannot have two stores that are named default in different Kubernetes namespaces.More info: https://doc.traefik.io/traefik/v3.0/https/tls/#certificates-stores
 ---
 
 # k8s_traefik_io_tls_store_v1alpha1_manifest (Data Source)