hashicorp · boruszak · May 1, 2024 · Apr 29, 2024 · Apr 29, 2024 · Apr 30, 2024
@@ -163,4 +163,4 @@ 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 Consul clusters to HCP Consul Central.
+all responses in order to support linking self-managed Enterprise clusters to HCP Consul Central.
@@ -25,7 +25,7 @@ The Consul control plane contains one or more _datacenters_. A datacenter is the
 
 ### Clusters
 
-A collection of Consul agents that are aware of each other is called a _cluster_. The terms _datacenter_ and _cluster_ are often used interchangeably. In some cases, however, _cluster_ refers only to Consul server agents, such as in [HCP Consul](https://cloud.hashicorp.com/products/consul). In other contexts, such as the [_admin partitions_](/consul/docs/enterprise/admin-partitions) feature included with Consul Enterprise, a cluster may refer to collection of client agents.
+A collection of Consul agents that are aware of each other is called a _cluster_. The terms _datacenter_ and _cluster_ are often used interchangeably. In some cases, however, _cluster_ refers only to Consul server agents, such as in [HCP Consu Dedicatedl](https://cloud.hashicorp.com/products/consul). In other contexts, such as the [_admin partitions_](/consul/docs/enterprise/admin-partitions) feature included with Consul Enterprise, a cluster may refer to collection of client agents.
 
 ## Agents
 

@@ -77,7 +77,7 @@ Consul server agents are an important part of Consul’s architecture. This sect
 
 Consul servers can be deployed on a few different runtimes:
 
-- **HashiCorp Cloud Platform (HCP) Consul (Managed)**. These Consul servers are deployed in a hosted environment managed by HCP. To get started with HCP Consul servers in Kubernetes or VM deployments, refer to the [Deploy HCP Consul tutorial](/consul/tutorials/get-started-hcp/hcp-gs-deploy).
+- **HashiCorp Cloud Platform (HCP) Consul Dedicated**. These Consul servers are deployed in a hosted environment managed by HCP. To get started with HCP Consul Dedicated servers in Kubernetes or VM deployments, refer to the [Deploy HCP Consul Dedicated tutorial](/consul/tutorials/get-started-hcp/hcp-gs-deploy).
 - **VMs or bare metal servers (Self-managed)**. To get started with Consul on VMs or bare metal servers, refer to the [Deploy Consul server tutorial](/consul/tutorials/get-started-vms/virtual-machine-gs-deploy). For a full list of configuration options, refer to [Agents Overview](/consul/docs/agent).
 - **Kubernetes (Self-managed)**. To get started with Consul on Kubernetes, refer to the [Deploy Consul on Kubernetes tutorial](/consul/tutorials/get-started-kubernetes/kubernetes-gs-deploy).
 - **Other container environments, including Docker, Rancher, and Mesos (Self-managed)**.

@@ -53,7 +53,8 @@ Be aware of the following constraints and technical limitations on the v2 catalo
 - The v1 and v2 catalog APIs cannot run concurrently. Because configuration entries are part of the v1 catalog, you cannot use them when the v2 catalog is enabled. Use v2 resources instead.
 - The Consul UI does not support the v2 catalog API in this release. You must disable the UI in the Helm chart in order to use the v2 catalog API.
 - Secondary datacenters in WAN-federated deployments cannot enable the v2 catalog API in this release.
-- HCP Consul does not support the v2 catalog API in this release. You cannot [link a self-managed cluster to HCP Consul](/hcp/docs/consul/self-managed) to access its UI or view observability metrics when it uses the v2 catalog.
+- HCP Consul Dedicated does not support the v2 catalog API in this release.
+- You cannot [link a self-managed cluster to HCP Consul Central](/hcp/docs/consul/self-managed) to access its UI or view observability metrics when it uses the v2 catalog.
 - We do not recommend updating existing clusters to enable the v2 catalog in this release. Instead, deploy a new Consul cluster and [enable the v2 catalog in the Helm chart](/consul/docs/k8s/multiport/configure#enable-the-v2-catalog).
 
 ## Guidance

@@ -82,7 +82,7 @@ Consul's service discovery capabilities help you discover, track, and monitor th
 
 You can use Consul with virtual machines (VMs), containers, serverless technologies, or with container orchestration platforms, such as [Nomad](https://www.nomadproject.io/) and Kubernetes. Consul is platform agnostic which makes it a great fit for all environments, including legacy platforms.
 
-Consul is available as a [self-managed](/consul/downloads) project or as a fully managed service mesh solution ([HCP Consul](https://portal.cloud.hashicorp.com/sign-in?utm_source=consul_docs)). HCP Consul enables users to discover and securely connect services without the added operational burden of maintaining a service mesh on their own.
+Consul is available as a [self-managed](/consul/downloads) project or as a fully managed service mesh solution ([HCP Consul Dedicated](https://portal.cloud.hashicorp.com/sign-in?utm_source=consul_docs)). HCP Consul Dedicated enables users to discover and securely connect services without the added operational burden of maintaining a service mesh on their own.
 
 ## Next steps
 

@@ -107,12 +107,12 @@ In simple terms, Consul is the control plane of the service mesh. The data plane
 You can use Consul with virtual machines (VMs), containers, or with container orchestration platforms, such as [Nomad](https://www.nomadproject.io/) and Kubernetes.
 Consul is platform agnostic which makes it a great fit for all environments, including legacy platforms.
 
-Consul is available as a [self-install](/consul/downloads) project or as a fully managed service mesh solution called [HCP Consul](https://portal.cloud.hashicorp.com/sign-in?utm_source=consul_docs).
-HCP Consul enables users to discover and securely connect services without the added operational burden of maintaining a service mesh on their own.
+Consul is available as a [self-install](/consul/downloads) project or as a fully managed service mesh solution called [HCP Consul Dedicated](https://portal.cloud.hashicorp.com/sign-in?utm_source=consul_docs).
+HCP Consul Dedicated enables users to discover and securely connect services without the added operational burden of maintaining a service mesh on their own.
 
 You can learn more about Consul by visiting the Consul [tutorials](/consul/tutorials).
 
 ## Next
 
-Get started today with a service mesh by leveraging [HCP Consul](https://portal.cloud.hashicorp.com/sign-in?utm_source=consul_docs).
+Get started today with a service mesh by leveraging [HCP Consul Dedicated](https://portal.cloud.hashicorp.com/sign-in?utm_source=consul_docs).
 Prepare your organization for the future of multi-cloud and embrace a [zero-trust](https://www.hashicorp.com/solutions/zero-trust-security) architecture.
@@ -71,11 +71,11 @@ 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 documentation
+### 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](/hcp/docs/consul/usage/cluster-peering/create-connections)
+- [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

@@ -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 guidance, refer to [Establish cluster peering connections on HCP Consul](/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). For HCP Consul Central guidance, refer to [Establish cluster peering connections on HCP Consul Central](/hcp/docs/consul/usage/cluster-peering/create-connections).
 
 ## Requirements
 

@@ -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 is supported.
+- HCP Consul Dedicated and HCP Consul Central are supported.
 - Consul API Gateway
 
 Consul Dataplane on ECS support the following features:
@@ -130,7 +130,7 @@ Consul Dataplane on ECS support the following features:
 - Mesh gateways
 - Running Consul service mesh in AWS Fargate and EC2
 - xDS load balancing
-- Self-managed and HCP Consul managed servers
+- Self-managed Enterprise and HCP Consul Dedicated servers
 
 ### Technical Constraints
 

@@ -121,10 +121,10 @@ Refer to the [Kubernetes `ReferenceGrant` documentation](https://gateway-api.sig
 
 ## Consul server deployments
 
-- Consul Enterprise and the free community edition are both supported.
+- Consul Enterprise and the community edition are both supported.
 - Supported Consul Server deployment types:
   - Self-Managed
-  - HCP Consul
+  - HCP Consul Dedicated
 
 ### Consul feature support
 

@@ -30,7 +30,7 @@ Refer to the following documentation and tutorials for additional guidance.
 
 ### Tutorials
 
-- [Integrate your AWS ECS services into Consul service mesh](/consul/tutorials/cloud-integrations/consul-ecs): Shows how to use Terraform to run Consul service mesh applications on ECS with self-managed Consul or HCP-managed Consul.
+- [Integrate your AWS ECS services into Consul service mesh](/consul/tutorials/cloud-integrations/consul-ecs): Shows how to use Terraform to run Consul service mesh applications on ECS with self-managed Enterprise or HCP Consul Dedicated.
 
 You can also refer to the following example configurations:
 

@@ -18,7 +18,7 @@ Consul on ECS supports the following environments, runtimes, and capabilities:
 - **Launch Types:** Fargate and EC2
 - **Network Modes:** `awsvpc`
 - **Subnets:** Private and public subnets. Tasks must have network access to Amazon ECR or other public container registries to pull images.
-- **Consul servers:** You can use your own Consul servers running on virtual machines or [use HCP Consul to host the servers for you](/hcp/docs/consul/hcp-managed).
+- **Consul servers:** You can use your own Consul servers running on virtual machines or [use HCP Consul Dedicated to host the servers for you](/hcp/docs/consul/dedicated).
 - **ECS controller:** The ECS controller assists with reconciling state back to Consul and facilitates Consul security features.
 - **Admin partitions:** <EnterpriseAlert inline/> Enable ACLs and configure the ECS controller to use admin partitions. You must deploy one controller for each admin partition. 
 - **Namespaces:** <EnterpriseAlert inline/> Enable ACLs and configure the ECS controller to use namespaces. 

@@ -65,17 +65,17 @@ The following features are [available in several forms of Consul Enterprise](#co
 ## Access Consul Enterprise
 
 The method of accessing Consul Enterprise and its features depends on the whether using
-HashiCorp Cloud Platform or self-managed Consul.
+HashiCorp Cloud Platform or self-managed Consul Enterprise.
 
-### HCP Consul
+### HCP Consul Dedicated
 
 No action is required to access Consul Enterprise in a
 [HashiCorp Cloud Platform](https://cloud.hashicorp.com/products/consul) installation.
 
-You can try out HCP Consul for free. Refer to the
-[HCP Consul product page](https://cloud.hashicorp.com/products/consul) for more details.
+You can try out HCP Consul Dedicated for free. Refer to the
+[HCP Consul Dedicated product page](https://cloud.hashicorp.com/products/consul) for more details.
 
-### Self-Managed Consul
+### Self-managed Consul Enterprise
 
 To access Consul Enterprise in a self-managed installation,
 [apply a purchased license](/consul/docs/enterprise/license/overview)

@@ -120,9 +120,9 @@ Contact your organization's [HashiCorp account team](https://support.hashicorp.c
 
 The license files are not locked to a specific cluster or cluster node. The above changes apply to all nodes in a cluster.
 
-## Q: Will this impact HCP Consul?
+## Q: Will this impact HCP Consul Dedicated?
 
-This will not impact HCP Consul.
+This will not impact HCP Consul Dedicated.
 
 ## Q: Does this need to happen every time a node restarts, or is this a one-time check?