Additional content migration

Author: boruszak

content/consul/v1.22.x/content/docs/automate/kv/store.mdx

@@ -89,5 +89,5 @@ Success! Deleted keys with prefix: redis
 ```
 
 <Warning title="Security warning">
-To mitigate vulnerability [CVE-2025-11392], Consul does not allow path escapes, directory escapes, leading spaces, or trailing spaces in keys, beginning with Consul v1.22.0. If you have any existing keys in this format and want to continue using the same keys, set the `disable_kv_key_validation` parameter to `true` in the Consul agent configuration. We strongly recommend using validated keys unless you have a specific reason to disable it for legacy compatibility.
+By default, Consul does not allow path escapes, directory escapes, leading spaces, or trailing spaces in keys, beginning with Consul v1.22.0. If you have any existing keys in this format and want to continue using the same keys, set the `disable_kv_key_validation` parameter to `true` in the Consul agent configuration. We strongly recommend using validated keys unless you have a specific reason to disable it for legacy compatibility.
 </Warning>

content/consul/v1.22.x/content/docs/integrate/index.mdx

@@ -10,7 +10,6 @@ description: >-
 The HashiCorp Consul Integration Program enables prospective partners to build integrations with HashiCorp Consul that are reviewed and verified by HashiCorp. You can integrate with any of the following Consul versions: 
 
 - **Self-Managed**. Community Edition, always free
-- **HashiCorp Cloud Platform (HCP)**. A hosted version of Consul managed in the cloud
 - **Consul Enterprise**. Self-managed, with additional features for custom deployments
 
 The program is intended to be largely self-service with links to resources, code samples, documentation, and clear integration steps.
@@ -35,7 +34,7 @@ By leveraging Consul's RESTful HTTP API system, prospective partners are able to
 
 **Infrastructure**: There are two integration options in this category: natively through a direct integration with Consul or via Consul-Terraform-Sync (CTS). By leveraging Consul's powerful **Network Infrastructure Automation (NIA)*** capabilities through CTS, changes in an infrastructure are seamlessly automated when Consul detects a change in its service catalog. For example, these integrations could be used to automate IP updates of load balancers or firewall security policies by leveraging Consul service discovery.
 
--> **Network Infrastructure Automation (NIA)***: These integrations leverage Consul's service catalog to seamlessly integrate with Consul-Terraform-Sync (CTS) to automate changes in network infrastructure via a publisher-subscriber method. Refer to the [NIA documentation](/consul/docs/integrate/nia) for details.
+-> **Network Infrastructure Automation (NIA)**: These integrations leverage Consul's service catalog to seamlessly integrate with Consul-Terraform-Sync (CTS) to automate changes in network infrastructure via a publisher-subscriber method. Refer to the [NIA documentation](/consul/docs/integrate/nia) for details.
 
 **Consul integration verification badges**: Partners will be issued the Consul Enterprise badge for integrations that work with [Consul Enterprise features](/consul/docs/enterprise) such as namespaces. Each badge would be displayed on HashiCorp's partner page as well as be available for posting on the partner's own website to provide better visibility and differentiation of the integration for joint customers.
 
@@ -113,11 +112,11 @@ Here are links to resources, documentation, examples and best practices to guide
 - [Consul Integration with Layer5 Meshery](https://www.hashicorp.com/integrations/layer5-io/consul)
 - [Consul Integration with VMware Tanzu Application Service](/consul/tutorials/cloud-integrations/sync-pivotal-cloud-services?utm_source=docs)
 
-#### Infrastructure:
+##### Infrastructure
 
 -> **Note**: The types of integration areas below could be developed to natively work with Consul or through leveraging Consul-Terraform-Sync and Consul's network automation capabilities. 
 
-**Firewalls**
+**Firewalls:**
 
   **Network Infrastructure Automation:**
 
@@ -134,11 +133,9 @@ Here are links to resources, documentation, examples and best practices to guide
 
 - [Load Balancing with NGINX and Consul Template](/consul/tutorials/load-balancing/load-balancing-nginx?utm_source=docs)
 - [Load Balancing with HAProxy Service Discovery](/consul/tutorials/load-balancing/load-balancing-haproxy?utm_source=docs)
-
-  **Network Infrastructure Automation:**
 
-  - [Zero-Touch Configuration of Secure Apps across BIG-IP Tenants using CTS](https://community.f5.com/t5/technical-articles/zero-touch-configuration-of-secure-apps-across-big-ip-tenants/ta-p/300190)
-  - [Automate VMware Advanced Load Balancers (Avi) with Consul NIA](https://www.hashicorp.com/integrations/_vmware/consul)
+- [Zero-Touch Configuration of Secure Apps across BIG-IP Tenants using CTS](https://community.f5.com/t5/technical-articles/zero-touch-configuration-of-secure-apps-across-big-ip-tenants/ta-p/300190)
+- [Automate VMware Advanced Load Balancers (Avi) with Consul NIA](https://www.hashicorp.com/integrations/_vmware/consul)
 
 **Application Delivery Controllers \(ADC\)**
 
@@ -148,7 +145,7 @@ Here are links to resources, documentation, examples and best practices to guide
 **Domain Name Service (DNS) Automation**
 
 - [Automate DNSimple public facing DNS records with Consul NIA](https://registry.terraform.io/modules/dnsimple/cts/dnsimple/latest)
-- [Automate NS1 managed DNS with Consul NIA](https://github.com/ns1-terraform/terraform-ns1-record-sync-nia)
+- [Automate UltraDNS with Consul-Terraform-Sync](https://github.com/ns1-terraform/terraform-ns1-record-sync-nia)
 
 **No-Code/Low-Code**
 

content/consul/v1.22.x/content/docs/reference/k8s/annotation-label.mdx

@@ -237,11 +237,13 @@ The following Kubernetes resource annotations could be used on a pod to control
   - `consul.hashicorp.com/consul-sidecar-cpu-request` - Override the default CPU request.
   - `consul.hashicorp.com/consul-sidecar-memory-limit` - Override the default memory limit.
   - `consul.hashicorp.com/consul-sidecar-memory-request` - Override the default memory request.
-  - `consul.hashicorp.com/enable-consul-dataplane-as-sidecar` - If this is set to `true`, then `consul-dataplane` will load as an init container and check the readiness using the startup probe. This will stall the initialisation of the application container until `consul-dataplane` is ready. Default value is `false`.
-  - `consul.hashicorp.com/sidecar-initial-probe-check-delay-seconds` - Number of seconds for the initial delay in Kubernetes before the startup probe starts checking the `consul-dataplane sidecar` container. Default value is `1`.
-  - `consul.hashicorp.com/sidecar-probe-period-seconds` - Number of seconds for the period between Kubernetes startup probe checks. Default value is `1`.
-  - `consul.hashicorp.com/sidecar-probe-failure-threshold` - Number of consecutive failures for the Kubernetes startup probe checks before restarting the `consul-dataplane` sidecar container. Default value is `1`.
-  - `consul.hashicorp.com/sidecar-probe-check-timeout-seconds` - Number of seconds for Kubernetes to trigger a timeout on startup probe checks.  Default value is `1`.
+
+- `consul.hashicorp.com/enable-consul-dataplane-as-sidecar` - If this is set to `true`, then `consul-dataplane` will load as an init container and check the readiness using the startup probe. This will stall the initialisation of the application container until `consul-dataplane` is ready. Default value is `false`.
+- `consul.hashicorp.com/sidecar-initial-probe-check-delay-seconds` - Number of seconds for the initial delay in Kubernetes before the startup probe starts checking the `consul-dataplane sidecar` container. Default value is `1`.
+- `consul.hashicorp.com/sidecar-probe-period-seconds` - Number of seconds for the period between Kubernetes startup probe checks. Default value is `1`.
+- `consul.hashicorp.com/sidecar-probe-failure-threshold` - Number of consecutive failures for the Kubernetes startup probe checks before restarting the `consul-dataplane` sidecar container. Default value is `1`.
+- `consul.hashicorp.com/sidecar-probe-check-timeout-seconds` - Number of seconds for Kubernetes to trigger a timeout on startup probe checks.  Default value is `1`.
+
 - `consul.hashicorp.com/enable-sidecar-proxy-lifecycle` - Override the default Helm value [`connectInject.sidecarProxy.lifecycle.defaultEnabled`](/consul/docs/reference/k8s/helm#v-connectinject-sidecarproxy-lifecycle-defaultenabled)
 - `consul.hashicorp.com/enable-sidecar-proxy-shutdown-drain-listeners` - Override the default Helm value [`connectInject.sidecarProxy.lifecycle.defaultEnableShutdownDrainListeners`](/consul/docs/reference/k8s/helm#v-connectinject-sidecarproxy-lifecycle-defaultenableshutdowndrainlisteners)
 - `consul.hashicorp.com/sidecar-proxy-lifecycle-shutdown-grace-period-seconds` - Override the default Helm value [`connectInject.sidecarProxy.lifecycle.defaultShutdownGracePeriodSeconds`](/consul/docs/reference/k8s/helm#v-connectinject-sidecarproxy-lifecycle-defaultshutdowngraceperiodseconds)

content/consul/v1.22.x/content/docs/vm.mdx

@@ -17,8 +17,8 @@ Consul supports service networking for application workloads on multiple runtime
 
 The following topics describe unique user actions, workflows, and goals related to installing Consul and operating it as a long-running daemon on multiple nodes in a network.
 
-- [Deploy Consul on VMs](/deploy/vm)
-- [Upgrade Consul on VMs](/upgrade/vm)
+- [Deploy Consul on VMs](/consul/docs/deploy/vm)
+- [Upgrade Consul on VMs](/consul/docs/upgrade/vm)
 
 ### Service networking on virtual machines