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

consul api-gateway kubernetes ecs service-discovery service-mesh vault

Go to file

R.B. Boyer 6393edba53 connect: reconcile how upstream configuration works with discovery chains (#6225 ) * connect: reconcile how upstream configuration works with discovery chains The following upstream config fields for connect sidecars sanely integrate into discovery chain resolution: - Destination Namespace/Datacenter: Compilation occurs locally but using different default values for namespaces and datacenters. The xDS clusters that are created are named as they normally would be. - Mesh Gateway Mode (single upstream): If set this value overrides any value computed for any resolver for the entire discovery chain. The xDS clusters that are created may be named differently (see below). - Mesh Gateway Mode (whole sidecar): If set this value overrides any value computed for any resolver for the entire discovery chain. If this is specifically overridden for a single upstream this value is ignored in that case. The xDS clusters that are created may be named differently (see below). - Protocol (in opaque config): If set this value overrides the value computed when evaluating the entire discovery chain. If the normal chain would be TCP or if this override is set to TCP then the result is that we explicitly disable L7 Routing and Splitting. The xDS clusters that are created may be named differently (see below). - Connect Timeout (in opaque config): If set this value overrides the value for any resolver in the entire discovery chain. The xDS clusters that are created may be named differently (see below). If any of the above overrides affect the actual result of compiling the discovery chain (i.e. "tcp" becomes "grpc" instead of being a no-op override to "tcp") then the relevant parameters are hashed and provided to the xDS layer as a prefix for use in naming the Clusters. This is to ensure that if one Upstream discovery chain has no overrides and tangentially needs a cluster named "api.default.XXX", and another Upstream does have overrides for "api.default.XXX" that they won't cross-pollinate against the operator's wishes. Fixes #6159		5 years ago
.circleci	Merge Consul OSS branch master at commit `b3541c4f34`	5 years ago
.github	Update questions issue template directing q's to the forum (#5957 )	6 years ago
acl	Fix to prevent allowing recursive KV deletions when we shouldn’t	6 years ago
agent	connect: reconcile how upstream configuration works with discovery chains (#6225 )	5 years ago
api	connect: allow L7 routers to match on http methods (#6164 )	5 years ago
bench	…
build-support	ui: modify content path (#5950 )	6 years ago
command	Update default gossip encryption key size to 32 bytes	5 years ago
connect	connect: Support RSA keys in addition to ECDSA (#6055 )	5 years ago
demo	…
ipaddr	Ensure Consul is IPv6 compliant (#5468 )	6 years ago
lib	resolve circleci config conflicts	5 years ago
logger	log rotation: limit count of rotated log files (#5831 )	5 years ago
sdk	resolve circleci config conflicts	5 years ago
sentinel	Update to use a consulent build tag instead of just ent (#5759 )	6 years ago
service_os	…
snapshot	Move internal/ to sdk/ (#5568 )	6 years ago
terraform	terraform: remove modules in repo (#5085 )	6 years ago
test	connect: reconcile how upstream configuration works with discovery chains (#6225 )	5 years ago
testrpc	Move internal/ to sdk/ (#5568 )	6 years ago
tlsutil	connect: Support RSA keys in addition to ECDSA (#6055 )	5 years ago
types	…
ui-v2	Merge remote-tracking branch 'origin/master' into release/1-6	5 years ago
vendor	Revert "connect: support AWS PCA as a CA provider" (#6251 )	5 years ago
version	Release v1.6.0-beta3	5 years ago
website	Update default gossip encryption key size to 32 bytes	5 years ago
.dockerignore	…
.gitignore	connect: Support RSA keys in addition to ECDSA (#6055 )	5 years ago
CHANGELOG.md	update changelog	5 years ago
GNUmakefile	Revert "connect: support AWS PCA as a CA provider" (#6251 )	5 years ago
INTERNALS.md	docs: correct link to top level agent package (#4750 )	6 years ago
LICENSE	…
NOTICE.md	…
README.md	Contribution guide (#4704 )	6 years ago
Vagrantfile	…
go.mod	Revert "connect: support AWS PCA as a CA provider" (#6251 )	5 years ago
go.sum	Revert "connect: support AWS PCA as a CA provider" (#6251 )	5 years ago
main.go	…
main_test.go	…

README.md

Consul

Website: https://www.consul.io
Chat: Gitter
Mailing list: Google Groups

Consul is a tool for service discovery and configuration. Consul is distributed, highly available, and extremely scalable.

Consul provides several key features:

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.
Multi-Datacenter - Consul is built to be datacenter aware, and can support any number of regions without complex configuration.
Service Segmentation - Consul Connect enables secure service-to-service communication with automatic TLS encryption and identity-based authorization.

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

An extensive quick start is viewable on the Consul website:

https://www.consul.io/intro/getting-started/install.html

Documentation

Full, comprehensive documentation is viewable on the Consul website:

https://www.consul.io/docs

Contributing

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