Go to file
freddygv d90240d367 Restore old Envoy prefix on escape hatches
This is done because after removing ID and NodeName from
ServiceConfigRequest we will no longer know whether a request coming in
is for a Consul client earlier than v1.10.
2021-03-15 14:12:57 -06:00
.changelog Add flags to consul connect envoy for metrics merging. (#9768) 2021-03-04 16:15:47 -06:00
.circleci xds: default to speaking xDS v3, but allow for v2 to be spoken upon request (#9658) 2021-02-26 16:23:15 -06:00
.github update changelog and website checks (#9781) 2021-02-26 16:29:49 -05:00
acl
agent Restore old Envoy prefix on escape hatches 2021-03-15 14:12:57 -06:00
api Restore old Envoy prefix on escape hatches 2021-03-15 14:12:57 -06:00
bench
build-support
command Restore old Envoy prefix on escape hatches 2021-03-15 14:12:57 -06:00
connect
contributing Update contrib docs for the new test name 2021-02-16 14:40:16 -05:00
demo
grafana
internal
ipaddr
lib
logging
proto
sdk
sentinel
service_os
snapshot
terraform
test xds: default to speaking xDS v3, but allow for v2 to be spoken upon request (#9658) 2021-02-26 16:23:15 -06:00
testrpc
tlsutil Fix main build failing 2021-02-05 17:25:57 -05:00
types
ui ui: Remove storybook, add docfy (#9831) 2021-03-08 12:22:01 +00:00
vendor xds: default to speaking xDS v3, but allow for v2 to be spoken upon request (#9658) 2021-02-26 16:23:15 -06:00
version
website Add flags to consul connect envoy for metrics merging. (#9768) 2021-03-04 16:15:47 -06:00
.dockerignore
.gitattributes
.gitignore
.golangci.yml xds: remove deprecated usages of xDS (#9602) 2021-02-22 15:00:15 -06:00
.hashibot.hcl
CHANGELOG.md changleog: presense -> presence (#9713) 2021-02-05 17:37:55 -05:00
GNUmakefile connect: connect CA Roots in the primary datacenter should use a SigningKeyID derived from their local intermediate (#9428) 2021-02-08 13:18:51 -06:00
INTERNALS.md
LICENSE
NOTICE.md
README.md
Vagrantfile
codecov.yml
go.mod
go.sum
main.go
main_test.go
package-lock.json

README.md

Consul CircleCI Discuss

Consul is a distributed, highly available, and data center aware solution to connect and configure applications across dynamic, distributed infrastructure.

Consul provides several key features:

  • Multi-Datacenter - Consul is built to be datacenter aware, and can support any number of regions without complex configuration.

  • Service Mesh/Service Segmentation - Consul Connect enables secure service-to-service communication with automatic TLS encryption and identity-based authorization. Applications can use sidecar proxies in a service mesh configuration to establish TLS connections for inbound and outbound connections without being aware of Connect at all.

  • Service Discovery - Consul makes it simple for services to register themselves and to discover other services via a DNS or HTTP interface. External services such as SaaS providers can be registered as well.

  • Health Checking - Health Checking enables Consul to quickly alert operators about any issues in a cluster. The integration with service discovery prevents routing traffic to unhealthy hosts and enables service level circuit breakers.

  • Key/Value Storage - A flexible key/value store enables storing dynamic configuration, feature flagging, coordination, leader election and more. The simple HTTP API makes it easy to use anywhere.

Consul runs on Linux, Mac OS X, FreeBSD, Solaris, and Windows. A commercial version called Consul Enterprise is also available.

Please note: We take Consul's security and our users' trust very seriously. If you believe you have found a security issue in Consul, please responsibly disclose by contacting us at security@hashicorp.com.

Quick Start

A few quick start guides are available on the Consul website:

Documentation

Full, comprehensive documentation is available on the Consul website:

https://www.consul.io/docs

Contributing

Thank you for your interest in contributing! Please refer to CONTRIBUTING.md for guidance.