Backport of Docs/CE-749-remove-references-from-consul into release/1.…

…20.x #21916 (#21917) Docs/CE-749-remove-references-from-consul (#21914) * delete HCP Consul Central references * Path correction * missed listing * Nav update Co-authored-by: Jeff Boruszak <[email protected]>
hashicorp · Nov 5, 2024 · 7f3976b · 7f3976b
1 parent 616f9ba
commit 7f3976b
Show file tree

Hide file tree

Showing 11 changed files with 7 additions and 299 deletions.
diff --git a/website/content/api-docs/api-structure.mdx b/website/content/api-docs/api-structure.mdx
@@ -159,8 +159,3 @@ UUID-format identifiers generated by the Consul API use the
 These UUID-format strings are generated using high quality, purely random bytes.
 It is not intended to be RFC compliant, merely to use a well-understood string
 representation of a 128-bit value.
-
-## CORS HTTP Response Headers
-
-As of Consul 1.18, Consul adds an HTTP header `Access-Control-Expose-Headers: x-consul-default-acl-policy` to
-all responses in order to support linking self-managed Enterprise clusters to HCP Consul Central.
diff --git a/website/content/api-docs/hcp-link.mdx b/website/content/api-docs/hcp-link.mdx
diff --git a/website/content/api-docs/index.mdx b/website/content/api-docs/index.mdx
@@ -49,7 +49,6 @@ The following API endpoints help you manage Consul operations.
 - [`/namespace`](/consul/api-docs/namespaces): Create and manage namespaces in Consul. Namespaces isolate groups of resources to lower operational overhead.
 - [`/snapshot`](/consul/api-docs/snapshot): Save and restore Consul server state in the event of a disaster.
 - [`/txn`](/consul/api-docs/txn): Apply multiple operations, such as updating the catalog and retrieving multiple KV entries, in a single transaction.
-- [`/api/hcp/v2/link/global`](/consul/api-docs/hcp-link): Link cluster to [HCP Consul Central](/hcp/docs/consul/concepts/consul-central). HCP Consul Central is a management plane service hosted by HashiCorp that enables you to monitor and manage Consul clusters.
 
 ## Configure your services dynamically
 

diff --git a/website/content/docs/connect/cluster-peering/index.mdx b/website/content/docs/connect/cluster-peering/index.mdx
@@ -70,13 +70,6 @@ The following resources are available to help you use Consul's cluster peering f
 - [Manage L7 traffic with cluster peering on Kubernetes](/consul/docs/k8s/connect/cluster-peering/usage/l7-traffic)
 - [Create sameness groups on Kubernetes](/consul/docs/k8s/connect/cluster-peering/usage/create-sameness-groups)
 
-### HCP Consul Central documentation
-
-- [Cluster peering](/hcp/docs/consul/usage/cluster-peering)
-- [Cluster peering topologies](/hcp/docs/consul/usage/cluster-peering/topologies)
-- [Establish cluster peering connections on HCP Consul Central](/hcp/docs/consul/usage/cluster-peering/create-connections)
-- [Cluster peering with HCP Consul Central](/hcp/docs/extend/cluster-peering/establish)
-
 ### Reference documentation
 
 - [Cluster peering technical specifications](/consul/docs/connect/cluster-peering/tech-specs)

diff --git a/website/content/docs/connect/cluster-peering/usage/create-sameness-groups.mdx b/website/content/docs/connect/cluster-peering/usage/create-sameness-groups.mdx
@@ -43,8 +43,6 @@ Mesh gateways are required for cluster peering connections and recommended to se
 
 You must establish connections with cluster peers before you can create a sameness group that includes them. A cluster peering connection exists between two admin partitions in different datacenters, and each connection between two partitions must be established separately with each peer. Refer to [establish cluster peering connections](/consul/docs/connect/cluster-peering/usage/establish-cluster-peering) for step-by-step instructions.
 
-You can establish and manage cluster peering relationships between all of your self-managed clusters using [HCP Consul Central](/hcp/docs/consul/concepts/consul-central). For more information, refer to [cluster peering global view](/hcp/docs/consul/monitor/consul-central/global-views#cluster-peering) in the HCP documentation.
-
 To establish cluster peering connections and define a group as part of the same workflow, follow instructions up to [Export services between clusters](/consul/docs/connect/cluster-peering/usage/establish-cluster-peering#export-services-between-clusters). You can use the same exported services and service intention configuration entries to establish the cluster peering connection and create the sameness group.
 
 ## Create a sameness group

diff --git a/website/content/docs/connect/cluster-peering/usage/establish-cluster-peering.mdx b/website/content/docs/connect/cluster-peering/usage/establish-cluster-peering.mdx
@@ -16,7 +16,7 @@ This page details the process for establishing a cluster peering connection betw
 
 Cluster peering between services cannot be established until all four steps are complete. If you want to establish cluster peering connections and create sameness groups at the same time, refer to the guidance in [create sameness groups](/consul/docs/connect/cluster-peering/usage/create-sameness-groups).
 
-For Kubernetes guidance, refer to [Establish cluster peering connections on Kubernetes](/consul/docs/k8s/connect/cluster-peering/usage/establish-peering). For HCP Consul Central guidance, refer to [Establish cluster peering connections on HCP Consul Central](/hcp/docs/consul/usage/cluster-peering/create-connections).
+For Kubernetes guidance, refer to [Establish cluster peering connections on Kubernetes](/consul/docs/k8s/connect/cluster-peering/usage/establish-peering).
 
 ## Requirements
 

diff --git a/website/content/docs/connect/dataplane/index.mdx b/website/content/docs/connect/dataplane/index.mdx
@@ -121,7 +121,7 @@ Consul Dataplane on Kubernetes supports the following features:
 - Running Consul service mesh in AWS Fargate and GKE Autopilot is supported.
 - xDS load balancing is supported.
 - Servers running in Kubernetes and servers external to Kubernetes are both supported.
-- HCP Consul Dedicated and HCP Consul Central are supported.
+- HCP Consul Dedicated is supported.
 - Consul API Gateway
 
 Consul Dataplane on ECS support the following features:

diff --git a/website/content/docs/k8s/connect/cluster-peering/usage/create-sameness-groups.mdx b/website/content/docs/k8s/connect/cluster-peering/usage/create-sameness-groups.mdx
@@ -43,8 +43,6 @@ Mesh gateways are required for cluster peering connections and recommended to se
 
 You must establish connections with cluster peers before you can create a sameness group that includes them. A cluster peering connection exists between two admin partitions in different datacenters, and each connection between two partitions must be established separately with each peer. Refer to [establish cluster peering connections](/consul/docs/k8s/connect/cluster-peering/usage/establish-peering) for step-by-step instructions.
 
-You can establish and manage cluster peering relationships between all of your self-managed clusters using [HCP Consul Central](/hcp/docs/consul/concepts/consul-central). For more information, refer to [cluster peering global view](/hcp/docs/consul/monitor/consul-central/global-views#cluster-peering) in the HCP documentation.
-
 To establish cluster peering connections and define a group as part of the same workflow, follow instructions up to [Export services between clusters](/consul/docs/k8s/connect/cluster-peering/usage/establish-peering#export-services-between-clusters). You can use the same exported services and service intention configuration entries to establish the cluster peering connection and create the sameness group.
 
 ## Create a sameness group