Go to file
Freddy 401f3010e0
Rename "cluster" config entry to "mesh" (#10127)
This config entry is being renamed primarily because in k8s the name
cluster could be confusing given that the config entry applies across
federated datacenters.

Additionally, this config entry will only apply to Consul as a service
mesh, so the more generic "cluster" name is not needed.
2021-04-28 16:13:29 -06:00
.changelog Rename "cluster" config entry to "mesh" (#10127) 2021-04-28 16:13:29 -06:00
.circleci remove Codecov from CI runs (#10145) 2021-04-28 13:23:31 -07:00
.github website: resolve unlinked content (#10087) 2021-04-23 10:51:13 -04:00
acl
agent Rename "cluster" config entry to "mesh" (#10127) 2021-04-28 16:13:29 -06:00
api Rename "cluster" config entry to "mesh" (#10127) 2021-04-28 16:13:29 -06:00
bench
build-support
command Rename "cluster" config entry to "mesh" (#10127) 2021-04-28 16:13:29 -06:00
connect connect/proxy: fix a number of problems with Listener 2021-04-28 17:21:35 -04:00
contributing
demo
grafana
internal
ipaddr
lib lib/ttlcache: never decrease the expiry on update 2021-04-21 15:32:26 -04:00
logging
proto
sdk submatview: fix godoc and comment typos 2021-04-28 12:27:38 -04:00
sentinel
service_os
snapshot
terraform
test test: switch envoy integration tests to use pkill instead of ps+grep+awk+kill (#10097) 2021-04-23 13:23:33 -05:00
testrpc
tlsutil
types
ui ui: Add TProxy Mode notice banner to service instance Upstreams tab (#10136) 2021-04-28 14:06:18 -04:00
vendor
version
website Rename "cluster" config entry to "mesh" (#10127) 2021-04-28 16:13:29 -06:00
.dockerignore
.gitattributes
.gitignore
.golangci.yml
.hashibot.hcl
CHANGELOG.md
GNUmakefile
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.