mirror of https://github.com/status-im/consul.git
HCP Consul Dedicated Rebrand changes (#21026)
* HCP Consul Dedicated rebrand * Dedicated rebrand * path change * Update website/content/docs/architecture/index.mdx Co-authored-by: Krastin Krastev <krastin@hashicorp.com> * typo --------- Co-authored-by: Krastin Krastev <krastin@hashicorp.com>
This commit is contained in:
Jeff Boruszak
GitHub
parent
b9296f8e65
commit
bbd8080ec0
|
|
@ -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 Consul Dedicated](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?
|
||||
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Consul ports reference
|
||||
description: Find information about the ports that Consul requires for its networking functions, including required ports for HCP Consul. Required ports differ for Consul servers and clients.
|
||||
description: Find information about the ports that Consul requires for its networking functions, including required ports for HCP Consul Dedicated. Required ports differ for Consul servers and clients.
|
||||
---
|
||||
|
||||
# Consul ports reference
|
||||
|
|
@ -16,13 +16,13 @@ The exact ports that Consul requires depend on your network's specific configura
|
|||
|
||||
There are slight differences between the port requirements for Consul servers and clients. When a Consul server has services, proxies, or gateways registered to it, then it acts as both a server and client.
|
||||
|
||||
HashiCorp-managed servers deployed using [HCP Consul](/hcp/docs/consul) have distinct port assignments. For more information, refer to [cluster management in the HCP documentation](https://developer.hashicorp.com/hcp/docs/consul/concepts/cluster-management#hashicorp-managed-clusters).
|
||||
[HCP Consul Dedicated servers](/hcp/docs/consul) have distinct port assignments. For more information, refer to [cluster management in the HCP documentation](https://developer.hashicorp.com/hcp/docs/consul/concepts/cluster-management#hashicorp-managed-clusters).
|
||||
|
||||
## Consul servers
|
||||
|
||||
The following table lists port names, their function, their network protocols, their default port numbers, whether they are enabled or disabled by default, port assignments for HashiCorp-managed server clusters, and the direction of traffic from the Consul server's perspective.
|
||||
The following table lists port names, their function, their network protocols, their default port numbers, whether they are enabled or disabled by default, port assignments for HCP Consul Dedicated server clusters, and the direction of traffic from the Consul server's perspective.
|
||||
|
||||
| Port name | Use | Protocol | Default port | Default status | HCP-managed port | Direction |
|
||||
| Port name | Use | Protocol | Default port | Default status | HCP Consul Dedicated port | Direction |
|
||||
| :------------------------ | :----------------------------------------- | :---------- | :----------- | :------------- | :--------------- | :-------------------- |
|
||||
| [DNS](#dns) | The DNS server | TCP and UDP | `8600` | Enabled | Unsupported | Incoming |
|
||||
| [HTTP](#http) | The HTTP API | TCP | `8500` | Enabled | Unsupported | Incoming |
|
||||
|
|
@ -47,7 +47,7 @@ The server's DNS port does not need to be open when DNS queries are sent to Cons
|
|||
|
||||
If you configure recursors in Consul to upstream DNS servers, then you need outbound access to those servers on port `53`.
|
||||
|
||||
To resolve Consul DNS requests when using HashiCorp-managed servers on HCP Consul, we recommend running Consul clients and resolving DNS against the clients. If your use case cannot accomodate this recommendation, open a support ticket.
|
||||
To resolve Consul DNS requests when using HCP Consul Dedicated, we recommend running Consul clients and resolving DNS against the clients. If your use case cannot accomodate this recommendation, open a support ticket.
|
||||
|
||||
### HTTP
|
||||
|
||||
|
|
@ -63,13 +63,13 @@ The server's HTTP port does not need to be open when Consul clients service all
|
|||
|
||||
The Consul CLI uses the HTTP port to interact with Consul by default.
|
||||
|
||||
HCP Consul does not support the HTTP port.
|
||||
HCP Consul Dedicated does not support the HTTP port.
|
||||
|
||||
### HTTPS
|
||||
|
||||
The following table lists information about the Consul server API's HTTPS port defaults:
|
||||
|
||||
| Default port | Protocol | Default status | Hashicorp-managed server port |
|
||||
| Default port | Protocol | Default status | HCP Consul Dedicated server port |
|
||||
| :----------- | :------- | :------------------ | :---------------------------- |
|
||||
| `8501` | TCP | Disabled by default | `443` |
|
||||
|
||||
|
|
@ -79,7 +79,7 @@ The server HTTPS port does not need to be open when Consul clients service all H
|
|||
|
||||
This port is disabled by default. You can enable it in the [agent configuration file](/consul/docs/agent/config/config-files#ports) or using the [`consul agent` CLI command](/consul/docs/agent/config/cli-flags).
|
||||
|
||||
HCP Consul assigns port `443` to HashiCorp-managed clusters, instead of the default `8501`.
|
||||
HCP Consul Dedicated assigns port `443` to HCP Consul Dedicated clusters, instead of the default `8501`.
|
||||
|
||||
### gRPC
|
||||
|
||||
|
|
@ -93,13 +93,13 @@ When using [Consul Dataplane](/consul/docs/connect/dataplane), this port receive
|
|||
|
||||
We recommend using gRPC TLS instead, so this port is disabled by default. You can enable it in the [agent configuration file](/consul/docs/agent/config/config-files#ports) or using the [`consul agent` CLI command](/consul/docs/agent/config/cli-flags).
|
||||
|
||||
HCP Consul does not support the gRPC port.
|
||||
HCP Consul Dedicated does not support the gRPC port.
|
||||
|
||||
### gRPC TLS
|
||||
|
||||
The following table lists information about the Consul API's gRPC with TLS port defaults:
|
||||
|
||||
| Default port | Protocol | Default status | Hashicorp-managed server port |
|
||||
| Default port | Protocol | Default status | HCP Consul Dedicated server port |
|
||||
| :----------- | :------- | :------------------ | :---------------------------- |
|
||||
| `8503` | TCP | Enabled by default | `8502` |
|
||||
|
||||
|
|
@ -113,7 +113,7 @@ In deployments with [cluster peering connections](/consul/docs/connect/cluster-p
|
|||
|
||||
In both local and remote cases, incoming traffic comes from the mesh gateways.
|
||||
|
||||
HCP Consul assigns port `8502` to HashiCorp-managed clusters, instead of the default `8503`.
|
||||
HCP Consul Dedicated assigns port `8502` to clusters, instead of the default `8503`.
|
||||
|
||||
When the [v2 catalog](/consul/docs/architecture/v2/catalog) is enabled, all API calls from external systems, such as the Consul CLI and Terraform provider, use this port.
|
||||
|
||||
|
|
@ -121,7 +121,7 @@ When the [v2 catalog](/consul/docs/architecture/v2/catalog) is enabled, all API
|
|||
|
||||
The following table lists information about the Server RPC port defaults:
|
||||
|
||||
| Default port | Protocol | Default status | Hashicorp-managed server port |
|
||||
| Default port | Protocol | Default status | HCP Consul Dedicated server port |
|
||||
| :----------- | :------- | :----------------- | :---------------------------- |
|
||||
| `8300` | TCP | Enabled by default | `8300` |
|
||||
|
||||
|
|
@ -135,7 +135,7 @@ When using WAN federation with mesh gateways, Consul servers must accept server
|
|||
|
||||
The following table lists information about the LAN serf port defaults:
|
||||
|
||||
| Default port | Protocol | Default status | Hashicorp-managed server port |
|
||||
| Default port | Protocol | Default status | HCP Consul Dedicated server port |
|
||||
| :----------- | :-----------| :----------------- | :---------------------------- |
|
||||
| `8301` | TCP and UDP | Enabled by default | `8301` |
|
||||
|
||||
|
|
@ -147,7 +147,7 @@ When running Enterprise deployments that use multiple admin partitions, all Cons
|
|||
|
||||
The following table lists information about the WAN serf port defaults:
|
||||
|
||||
| Default port | Protocol | Default status | Hashicorp-managed server port |
|
||||
| Default port | Protocol | Default status | HCP Consul Dedicated server port |
|
||||
| :----------- | :---------- | :----------------- | :---------------------------- |
|
||||
| `8302` | TCP and UDP | Enabled by default | `8302` |
|
||||
|
||||
|
|
|
|||
|
|
@ -17,7 +17,7 @@ The program is intended to be largely self-service with links to resources, code
|
|||
|
||||
## Categories of Consul Integrations
|
||||
|
||||
By leveraging Consul's RESTful HTTP API system, prospective partners are able to build extensible integrations at the data plane, platform, and the infrastructure layer to extend Consul's functionalities. These integrations can be performed both with the community edition of Consul, Consul Enterprise, and HCP Consul.
|
||||
By leveraging Consul's RESTful HTTP API system, prospective partners are able to build extensible integrations at the data plane, platform, and the infrastructure layer to extend Consul's functionalities. These integrations can be performed both with the community edition of Consul, Consul Enterprise, and HCP Consul Dedicated.
|
||||
|
||||
**The Consul ecosystem of integrations:**
|
||||
|
||||
|
|
@ -37,9 +37,9 @@ By leveraging Consul's RESTful HTTP API system, prospective partners are able to
|
|||
|
||||
-> **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-integration) for details.
|
||||
|
||||
**HCP Consul**: HCP Consul is secure by default and offers an out-of-the-box service mesh solution to streamline operations without the hassle of managing Consul servers. [Sign up for a free HCP Consul account](https://cloud.hashicorp.com/products/consul).
|
||||
**HCP Consul Dedicated**: HCP Consul Dedicated is secure by default and offers an out-of-the-box service mesh solution to streamline operations without the hassle of managing Consul servers. [Sign up for a free HCP Consul Dedicated account](https://cloud.hashicorp.com/products/consul).
|
||||
|
||||
**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. Partners will be issued the HCP Consul badge for integrations validated to work with [HCP Consul](/hcp/docs/consul#features). 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.
|
||||
**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. Partners will be issued the HCP Consul Dedicated badge for integrations validated to work with [HCP Consul Dedicated](/hcp/docs/consul#features). 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.
|
||||
|
||||
<span style={{display:'block', textAlign:'center'}}>
|
||||
<ImageConfig inline height={192} width={192}>
|
||||
|
|
@ -49,12 +49,12 @@ By leveraging Consul's RESTful HTTP API system, prospective partners are able to
|
|||
</ImageConfig>
|
||||
<ImageConfig inline height={192} width={192}>
|
||||
|
||||
|
||||
|
||||
|
||||
</ImageConfig>
|
||||
</span>
|
||||
|
||||
Developing a valid integration with either Consul Enterprise or HCP Consul also qualifies the partner for the Premier tier of the HashiCorp Technology Partners program. The process for verification of these integrations is detailed below.
|
||||
Developing a valid integration with either Consul Enterprise or HCP Consul Dedicated also qualifies the partner for the Premier tier of the HashiCorp Technology Partners program. The process for verification of these integrations is detailed below.
|
||||
|
||||
## Development Process
|
||||
|
||||
|
|
@ -87,7 +87,7 @@ Here are links to resources, documentation, examples and best practices to guide
|
|||
|
||||
- [Consul Telemetry Documentation](/consul/docs/agent/telemetry)
|
||||
- [Monitoring Consul with Datadog APM](https://www.datadoghq.com/blog/consul-datadog/)
|
||||
- [Monitor HCP Consul with New Relic Instant Observability](https://github.com/newrelic-experimental/hashicorp-quickstart-annex/blob/main/hcp-consul/README.md)
|
||||
- [Monitor HCP Consul Dedicated with New Relic Instant Observability](https://github.com/newrelic-experimental/hashicorp-quickstart-annex/blob/main/hcp-consul/README.md)
|
||||
- [HCP Consul and CloudFabrix AIOps Integration](https://bot-docs.cloudfabrix.io/Bots/consul/?h=consul)
|
||||
- [Consul and SnappyFlow Full Stack Observability](https://docs.snappyflow.io/docs/Integrations/hcp_consul)
|
||||
|
||||
|
|
@ -167,17 +167,17 @@ Here are links to resources, documentation, examples and best practices to guide
|
|||
|
||||
The only knowledge necessary to write a plugin is basic command-line skills and knowledge of the [Go programming language](http://www.golang.org). Use the plugin interface to develop your integration. All integrations should contain unit and acceptance testing.
|
||||
|
||||
**HCP Consul**: As a managed service, minimal configuration is required to deploy HCP Consul server clusters. You only need to install Consul client agents. Furthermore, HashiCorp provides all new users an initial credit, which provides approximately two months worth of [development cluster](https://cloud.hashicorp.com/products/consul/pricing) access. When deployed with AWS or Azure free tier services, there should be no cost beyond the time spent by the designated tester. Refer to the [Deploy HCP Consul tutorial](/consul/tutorials/get-started-hcp/hcp-gs-deploy) for details on getting started.
|
||||
**HCP Consul Dedicated**: As a managed service, minimal configuration is required to deploy HCP Consul Dedicated server clusters. You only need to install Consul client agents. Furthermore, HashiCorp provides all new users an initial credit, which provides approximately two months worth of [development cluster](https://cloud.hashicorp.com/products/consul/pricing) access. When deployed with AWS or Azure free tier services, there should be no cost beyond the time spent by the designated tester. Refer to the [Deploy HCP Consul Dedicated tutorial](/consul/tutorials/get-started-hcp/hcp-gs-deploy) for details on getting started.
|
||||
|
||||
HCP Consul is currently only deployed on AWS and Microsoft Azure, so your application can be deployed to or run in AWS or Azure.
|
||||
HCP Consul Dedicated is currently only deployed on AWS and Microsoft Azure, so your application can be deployed to or run in AWS or Azure.
|
||||
|
||||
#### HCP Consul Resource Links:
|
||||
#### HCP Consul Dedicated Resource Links:
|
||||
|
||||
- [Getting Started with HCP Consul](/consul/tutorials/get-started-hcp/hcp-gs-deploy)
|
||||
- [HCP Consul End-to-End Deployment](/consul/tutorials/cloud-deploy-automation/consul-end-to-end-overview)
|
||||
- [Deploy HCP Consul with EKS using Terraform](/consul/tutorials/cloud-deploy-automation/consul-end-to-end-eks)
|
||||
- [HCP Consul Deployment Automation](/consul/tutorials/cloud-deploy-automation)
|
||||
- [HCP Consul documentation](/hcp/docs/consul/usage)
|
||||
- [Getting Started with HCP Consul Dedicated](/consul/tutorials/get-started-hcp/hcp-gs-deploy)
|
||||
- [HCP Consul Dedicated End-to-End Deployment](/consul/tutorials/cloud-deploy-automation/consul-end-to-end-overview)
|
||||
- [Deploy HCP Consul Dedicated with EKS using Terraform](/consul/tutorials/cloud-deploy-automation/consul-end-to-end-eks)
|
||||
- [HCP Consul Dedicated Deployment Automation](/consul/tutorials/cloud-deploy-automation)
|
||||
- [HCP Consul Dedicated documentation](/hcp/docs/consul/usage)
|
||||
|
||||
**Consul Enterprise**: An integration qualifies for Consul Enterprise when it is tested and compatible with Consul Enterprise Namespaces.
|
||||
|
||||
|
|
|
|||
|
|
@ -77,7 +77,7 @@ Rolling out changes can be risky, especially in complex network environments. Up
|
|||
|
||||
HashiCorp offers core Consul functionality for free in the community edition, which is ideal for smaller businesses and teams that want to pilot Consul within their organizations. As your business grows, you can upgrade to Consul Enterprise, which offers additional capabilities designed to address organizational complexities of collaboration, operations, scale, and governance.
|
||||
|
||||
### HCP Consul
|
||||
### HCP Consul Dedicated
|
||||
|
||||
HashiCorp Cloud Platform (HCP) Consul is our SaaS that delivers Consul Enterprise capabilities and shifts the burden of managing the control plane to us. Create an HCP organization and leverage our expertise to simplify control plane maintenance and configuration. Learn more at [HashiCorp Cloud Platform](https://cloud.hashicorp.com/products/consul).
|
||||
|
||||
|
|
|
|||
|
|
@ -693,7 +693,7 @@ Use these links to navigate to a particular top-level stanza.
|
|||
This can either be used to [configure a new cluster](/hcp/docs/consul/self-managed/new)
|
||||
or [link an existing one](/hcp/docs/consul/self-managed/existing).
|
||||
|
||||
Note: this setting should not be enabled for [HashiCorp-managed clusters](/hcp/docs/consul/hcp-managed).
|
||||
Note: this setting should not be enabled for [HCP Consul Dedicated clusters](/hcp/docs/consul/dedicated).
|
||||
It is strictly for linking self-managed clusters.
|
||||
|
||||
- `resourceId` ((#v-global-cloud-resourceid)) - The resource id of the HCP Consul Central cluster to link to. Eg:
|
||||
|
|
@ -2841,8 +2841,8 @@ Use these links to navigate to a particular top-level stanza.
|
|||
- `resourceId` ((#v-telemetrycollector-cloud-resourceid)) - The resource id of the HCP Consul Central cluster to push metrics for. Eg:
|
||||
`organization/27109cd4-a309-4bf3-9986-e1d071914b18/project/fcef6c24-259d-4510-bb8d-1d812e120e34/hashicorp.consul.global-network-manager.cluster/consul-cluster`
|
||||
|
||||
This is used for HCP Consul Central-linked or managed clusters where global.cloud.resourceId is unset. For example, when using externalServers
|
||||
with HCP Consul-managed clusters or HCP Consul Central-linked clusters in a different admin partition.
|
||||
This is used for HCP Consul Central-linked or HCP Consul Dedicated clusters where global.cloud.resourceId is unset. For example, when using externalServers
|
||||
with HCP Consul Dedicated clusters or HCP Consul Central-linked clusters in a different admin partition.
|
||||
|
||||
If global.cloud.resourceId is set, this should either be unset (defaulting to global.cloud.resourceId) or be the same as global.cloud.resourceId.
|
||||
|
||||
|
|
|
|||
|
|
@ -41,7 +41,8 @@ Be aware of the following constraints and technical limitations on using multi-p
|
|||
- When running the v2 catalog for multi-port services, you cannot run the v1 catalog API at the same time.
|
||||
- Because configuration entries are part of the v1 catalog, you cannot use them when the v2 catalog is enabled. Use v2 resources instead to configure multi-port service behavior in the service mesh.
|
||||
- The Consul UI does not support multi-port services in this release. You must disable the UI in the Helm chart in order to use multi-port services.
|
||||
- HCP Consul does not support multi-port services 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 multi-port services in this release.
|
||||
- You cannot [link a self-managed Enterprise 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. To register multi-port services, deploy a new Consul cluster that enables the v2 catalog.
|
||||
|
||||
## Guidance
|
||||
|
|
|
|||
|
|
@ -13,7 +13,7 @@ This topic describes Consul-Terraform-Sync (CTS) cross-compatibility with Consul
|
|||
|
||||
Below are CTS versions with supported Consul versions. The latest CTS binary supports the three most recent Consul minor versions, along with their latest patch versions.
|
||||
|
||||
| CTS Version | Consul Community Edition & Enterprise Version | HCP Consul Version |
|
||||
| CTS Version | Consul Community Edition & Enterprise Version | HCP Consul Dedicated Version |
|
||||
| :--------------------- | :------------------------------ | :----------------- |
|
||||
| CTS Enterprise 0.6+ | 1.8+ | 1.9+ |
|
||||
| CTS Enterprise 0.3-0.5 | 1.8+ | N/A |
|
||||
|
|
|
|||
|
|
@ -86,7 +86,7 @@ license {
|
|||
|
||||
You can use the `auto_retrieval` block to configure the automatic license retrieval in CTS. When enabled, CTS attempts to retrieve a new license from its configured Consul Enterprise backend once a day. If CTS cannot retrieve a license and the current license is reaching its expiration date, CTS attempts to retrieve a license with increased frequency, as defined by the [License Expiration Date Handling](/consul/docs/nia/enterprise/license#license-expiration-handling).
|
||||
|
||||
~> Enabling `auto_retrieval` is recommended when using HCP Consul, as HCP Consul licenses expire more frequently than Consul Enterprise licenses. Without auto-retrieval enabled, you have to restart CTS every time you load a new license.
|
||||
~> Enabling `auto_retrieval` is recommended when using HCP Consul Dedicated, as HCP Consul Dedicated licenses expire more frequently than Consul Enterprise licenses. Without auto-retrieval enabled, you have to restart CTS every time you load a new license.
|
||||
|
||||
| Parameter | Required | Type | Description | Default |
|
||||
| --------- | -------- | ---- | ----------- | ------- |
|
||||
|
|
|
|||
|
|
@ -20,7 +20,7 @@ To get a trial license for CTS, you can sign-up for the [trial license for Consu
|
|||
## Automatic License Retrieval
|
||||
CTS automatically retrieves a license from Consul on startup and then attempts to retrieve a new license once a day. If the current license is reaching its expiration date, CTS attempts to retrieve a license with increased frequency, as defined by the [License Expiration Date Handling](/consul/docs/nia/enterprise/license#license-expiration-handling).
|
||||
|
||||
~> Enabling automatic license retrieval is recommended when using HCP Consul, as HCP Consul licenses expire more frequently than Consul Enterprise licenses. Without auto-retrieval enabled, you have to restart CTS every time you load a new license.
|
||||
~> Enabling automatic license retrieval is recommended when using HCP Consul Dedicated, as HCP Consul Dedicated licenses expire more frequently than Consul Enterprise licenses. Without auto-retrieval enabled, you have to restart CTS every time you load a new license.
|
||||
|
||||
## Setting the License Manually
|
||||
|
||||
|
|
|
|||
|
|
@ -36,7 +36,7 @@ This release includes the following features and capabilities:
|
|||
- Google GKE
|
||||
- Azure AKS.
|
||||
1. Install via the HashiCorp Consul Helm chart.
|
||||
1. Works with self-managed Consul servers and HCP Consul servers
|
||||
1. Works with self-managed Consul Enterprise servers and HCP Consul Dedicated servers
|
||||
1. Configure via Kubernetes Gateway API - v1alpha2
|
||||
1. Deploy 1 or more logical API Gateways per Kubernetes cluster
|
||||
1. Support for HTTP, HTTPS, TCP, and TCP+TLS
|
||||
|
|
|
|||
|
|
@ -16,7 +16,7 @@ Catalog v2 supports multi-port application deployments with a single Envoy proxy
|
|||
|
||||
The v1 and v2 catalogs are not cross compatible, and not all Consul features are available within this v2 feature preview.
|
||||
- The Consul UI must be disabled. It does not support multi-port services or the v2 catalog API in this release.
|
||||
- HCP Consul does not support multi-port services or the v2 catalog API in this release.
|
||||
- HCP Consul Dedicated does not support multi-port services or the v2 catalog API in this release.
|
||||
- The v2 API only supports transparent proxy mode where services that have permissions to connect to each other can use Kube DNS to connect.
|
||||
|
||||
<Note> The v2 Catalog and Resources API is currently in feature preview for Consul on Kubernetes 1.3.0 and should not be used in production environments. </Note>
|
||||
|
|
|
|||
|
|
@ -16,9 +16,9 @@ We have implemented the following features in this release:
|
|||
|
||||
You can now execute Terraform tasks in `remote` or `cloud agent` mode. For more information, refer to the [per-task execution mode documentation](/consul/docs/nia/network-drivers/terraform-cloud#remote-workspaces).
|
||||
|
||||
### HCP Consul Support <EnterpriseAlert inline />
|
||||
### HCP Consul Dedicated Support <EnterpriseAlert inline />
|
||||
|
||||
CTS now supports interoperability with HCP Consul. CTS retrieves licenses from HCP Consul so that users can keep their HCP Consul license or Consul enterprise deployment license in sync.
|
||||
CTS now supports interoperability with HCP Consul Dedicated. CTS retrieves licenses from HCP Consul Dedicated so that users can keep their HCP Consul Dedicated license or Consul enterprise deployment license in sync.
|
||||
|
||||
### Auto Service-registration with Consul and Health API Endpoint
|
||||
|
||||
|
|
@ -36,7 +36,7 @@ CTS includes a new [API endpoint](/consul/docs/nia/api/health#health) that provi
|
|||
## Supported Software Versions
|
||||
|
||||
- Consul: v1.9+
|
||||
- <EnterpriseAlert inline /> HCP Consul: Latest
|
||||
- <EnterpriseAlert inline /> HCP Consul Dedicated: Latest
|
||||
- Terraform CLI: v0.13 - v1.1
|
||||
- <EnterpriseAlert inline /> HCP Terraform: Latest
|
||||
- <EnterpriseAlert inline /> Terraform Enterprise: v202010-2 - Latest
|
||||
|
|
|
|||
|
|
@ -49,7 +49,7 @@
|
|||
"path": "install"
|
||||
},
|
||||
{
|
||||
"title": "Learn HCP Consul",
|
||||
"title": "Learn HCP Consul Dedicated",
|
||||
"href": "https://developer.hashicorp.com/consul/tutorials/get-started-hcp"
|
||||
},
|
||||
{
|
||||
|
|
@ -1852,7 +1852,7 @@
|
|||
"divider": true
|
||||
},
|
||||
{
|
||||
"title": "HCP Consul",
|
||||
"title": "HCP Consul Dedicated",
|
||||
"href": "https://cloud.hashicorp.com/docs/consul"
|
||||
},
|
||||
{
|
||||
|
|
|
|||
Loading…
Reference in New Issue