mirror of https://github.com/status-im/consul.git
Broken link fixes (#16566)
This commit is contained in:
parent
58016d1aa2
commit
3d75ab8a41
|
@ -90,6 +90,6 @@ Get started with service discovery today by leveraging Consul on HCP, Consul on
|
|||
|
||||
Feel free to get started with Consul by exploring one of these Consul tutorials:
|
||||
|
||||
- [Get Started with Consul on VMs](/consul/tutorials/getting-started)
|
||||
- [Get Started with Consul on HCP](/consul/tutorials/cloud-get-started)
|
||||
- [Get Started with Consul on Kubernetes](/consul/tutorials/gs-consul-service-mesh)
|
||||
- [Get Started with Consul on VMs](/consul/tutorials/get-started-vms)
|
||||
- [Get Started with Consul on HCP](/consul/tutorials/get-started-hcp)
|
||||
- [Get Started with Consul on Kubernetes](/consul/tutorials/get-started-kubernetes)
|
|
@ -10,9 +10,9 @@ description: >-
|
|||
HashiCorp Consul is a service networking solution that enables teams to manage secure network connectivity between services and across on-prem and multi-cloud environments and runtimes. Consul offers service discovery, service mesh, traffic management, and automated updates to network infrastructure device. You can use these features individually or together in a single Consul deployment.
|
||||
|
||||
> **Hands-on**: Complete the Getting Started tutorials to learn how to deploy Consul:
|
||||
- [Get Started on Kubernetes](/consul/tutorials/gs-consul-service-mesh)
|
||||
- [Get Started on VMs](/consul/tutorials/getting-started)
|
||||
- [HashiCorp Cloud Platform (HCP) Consul](/consul/tutorials/cloud-get-started)
|
||||
- [Get Started on Kubernetes](/consul/tutorials/get-started-kubernetes)
|
||||
- [Get Started on VMs](/consul/tutorials/get-started-vms)
|
||||
- [HashiCorp Cloud Platform (HCP) Consul](/consul/tutorials/get-started-hcp)
|
||||
|
||||
## How does Consul work?
|
||||
|
||||
|
|
|
@ -31,7 +31,7 @@ For information on compatible Consul versions, refer to the [Consul compatibilit
|
|||
|
||||
### Run an agent
|
||||
|
||||
The Consul agent must be running in order to dynamically update network devices. Refer to the [Consul agent documentation](/consul/docs/agent) for information about configuring and starting a Consul agent. For hands-on instructions about running Consul agents, refer to the [Getting Started: Run the Consul Agent Tutorial](/consul/tutorials/getting-started/get-started-agent).
|
||||
The Consul agent must be running in order to dynamically update network devices. Refer to the [Consul agent documentation](/consul/docs/agent) for information about configuring and starting a Consul agent.
|
||||
|
||||
When running a Consul agent with CTS in production, consider that CTS uses [blocking queries](/consul/api-docs/features/blocking) to monitor task dependencies, such as changes to registered services. This results in multiple long-running TCP connections between CTS and the agent to poll changes for each dependency. Consul may quickly reach the agent connection limits if CTS is monitoring a high number of services.
|
||||
|
||||
|
@ -62,11 +62,11 @@ You can configure CTS to monitor the web service, execute a task, and update net
|
|||
|
||||
For more details on registering a service using the HTTP API endpoint, refer to the [register service API docs](/consul/api-docs/agent/service#register-service).
|
||||
|
||||
For hands-on instructions on registering a service by loading a service definition, refer to the [Getting Started: Register a Service with Consul Service Discovery Tutorial](/consul/tutorials/getting-started/get-started-service-discovery).
|
||||
For hands-on instructions on registering a service by loading a service definition, refer to the [Getting Started: Register a Service with Consul Service Discovery Tutorial](/consul/tutorials/get-started-vms/virtual-machine-gs-service-discovery).
|
||||
|
||||
### Run a cluster
|
||||
|
||||
For production environments, we recommend operating a Consul cluster rather than a single agent. Refer to [Getting Started: Create a Local Consul Datacenter](/consul/tutorials/getting-started/get-started-create-datacenter) for instructions on starting multiple Consul agents and joining them into a cluster.
|
||||
For production environments, we recommend operating a Consul cluster rather than a single agent. Refer to [Getting Started: Deploy a Consul Datacenter Tutorial](/consul/tutorials/get-started-vms/virtual-machine-gs-deploy) for instructions on starting multiple Consul agents and joining them into a cluster.
|
||||
|
||||
## Network infrastructure using a Terraform provider
|
||||
|
||||
|
|
Loading…
Reference in New Issue