mirror of https://github.com/hashicorp/consul
Added a note at the being of each doc to notify users about the temporary repo change.
parent
13b49df77b
commit
9a2a8781f9
|
@ -9,6 +9,8 @@ description: >
|
|||
as data loss is inevitable in a failure scenario.
|
||||
---
|
||||
|
||||
**Note: This guide is temporarily being managed in a different repo. Please contact kait@hashicorp.com if you have any questions.
|
||||
|
||||
# Run the Consul Agent
|
||||
|
||||
After Consul is installed, the agent must be run. The agent can run either
|
||||
|
|
|
@ -6,6 +6,9 @@ description: |-
|
|||
We've now seen how simple it is to run Consul, add nodes and services, and query those nodes and services. In this step, we will continue our tour by adding health checks to both nodes and services. Health checks are a critical component of service discovery that prevent using services that are unhealthy.
|
||||
---
|
||||
|
||||
**Note: This guide is temporarily being managed in a different repo. Please contact kait@hashicorp.com if you have any
|
||||
questions.
|
||||
|
||||
# Health Checks
|
||||
|
||||
We've now seen how simple it is to run Consul, add nodes and services, and
|
||||
|
|
|
@ -6,6 +6,9 @@ description: |-
|
|||
Connect is a feature of Consul that provides service-to-service connection authorization and encryption using mutual TLS. This ensures that all service communication in your datacenter is encrypted and that the rules of what services can communicate is centrally managed with Consul.
|
||||
---
|
||||
|
||||
**Note: This guide is temporarily being managed in a different repo. Please contact kait@hashicorp.com if you have any
|
||||
questions.
|
||||
|
||||
# Connect
|
||||
|
||||
We've now registered our first service with Consul and we've shown how you
|
||||
|
|
|
@ -6,6 +6,9 @@ description: |-
|
|||
Consul must first be installed on every node that will be a member of the Consul cluster. To make installation easy, Consul is distributed as a binary package for all supported platforms and architectures. This page will not cover how to compile Consul from source.
|
||||
---
|
||||
|
||||
**Note: This guide is temporarily being managed in a different repo. Please contact kait@hashicorp.com if you have any
|
||||
questions.
|
||||
|
||||
# Install Consul
|
||||
|
||||
Consul must first be installed on your machine. Consul is distributed as a
|
||||
|
|
|
@ -9,6 +9,9 @@ description: >
|
|||
cluster and join the nodes together.
|
||||
---
|
||||
|
||||
**Note: This guide is temporarily being managed in a different repo. Please contact kait@hashicorp.com if you have any
|
||||
questions.
|
||||
|
||||
# Consul Cluster
|
||||
|
||||
We've started our first agent and registered and queried a service on that
|
||||
|
|
|
@ -6,6 +6,9 @@ description: |-
|
|||
In addition to providing service discovery and integrated health checking, Consul provides an easy to use KV store. This can be used to hold dynamic configuration, assist in service coordination, build leader election, and enable anything else a developer can think to build.
|
||||
---
|
||||
|
||||
**Note: This guide is temporarily being managed in a different repo. Please contact kait@hashicorp.com if you have any
|
||||
questions.
|
||||
|
||||
# KV Data
|
||||
|
||||
In addition to providing service discovery and integrated health checking,
|
||||
|
|
|
@ -6,6 +6,9 @@ description: |-
|
|||
That concludes the getting started guide for Consul. Hopefully you're able to see that while Consul is simple to use, it has a powerful set of features. We've covered the basics for all of these features in this guide.
|
||||
---
|
||||
|
||||
**Note: This guide is temporarily being managed in a different repo. Please contact kait@hashicorp.com if you have any
|
||||
questions.
|
||||
|
||||
# Next Steps
|
||||
|
||||
That concludes the getting started guide for Consul. Hopefully you're able to
|
||||
|
|
|
@ -9,6 +9,9 @@ description: >
|
|||
query that service using the REST API and DNS interfaces.
|
||||
---
|
||||
|
||||
**Note: This guide is temporarily being managed in a different repo. Please contact kait@hashicorp.com if you have any
|
||||
questions.
|
||||
|
||||
# Registering Services
|
||||
|
||||
In the previous step, we ran our first agent, saw the cluster members (well,
|
||||
|
|
|
@ -6,6 +6,9 @@ description: |-
|
|||
Consul comes with support for beautiful, functional web UIs out of the box. UIs can be used for viewing all services and nodes, for viewing all health checks and their current status, and for reading and setting key/value data. The UIs automatically supports multi-datacenter.
|
||||
---
|
||||
|
||||
**Note: This guide is temporarily being managed in a different repo. Please contact kait@hashicorp.com if you have any
|
||||
questions.
|
||||
|
||||
# Consul Web UI
|
||||
|
||||
Consul comes with support for beautiful, functional web UIs out of the
|
||||
|
|
Loading…
Reference in New Issue