Go to file
trujillo-adam e4f243c402 removed most of 'ECS service' information 2022-06-21 17:02:18 -07:00
.changelog ui: Fix intl keys in order to render correct messages for empty states (#13409) 2022-06-16 12:07:04 +01:00
.circleci Load test, upgrade packer version, fix k6s installation (#13382) 2022-06-15 09:29:38 -04:00
.github correct redgat_tag ospid 2022-06-16 13:28:36 +01:00
.release
acl Move ACLResolveResult into acl/resolver package (#13467) 2022-06-17 10:24:43 +01:00
agent state: peering ID assignment cannot happen inside of the state store (#13525) 2022-06-21 13:04:08 -05:00
api Add leader routine to clean up peerings 2022-06-14 15:36:50 -06:00
bench
build-support Minor cleanup for build-date script 2022-06-09 17:07:41 -07:00
command [OSS] Support merge-central-config option in node services list API (#13450) 2022-06-15 08:30:31 -07:00
connect
contributing
docs docs: instructions for interacting with the private gRPC server locally 2022-06-15 18:26:58 +01:00
grafana
internal
ipaddr
lib
logging
proto xds: mesh gateways now have their own leaf certificate when involved in a peering (#13460) 2022-06-15 14:36:18 -05:00
proto-public
sdk
sentinel
service_os
snapshot
test update github.com/containerd/containerd to 1.5.13 (#13520) 2022-06-21 12:20:00 -04:00
testrpc
tlsutil
tools/private-grpc-proxy docs: instructions for interacting with the private gRPC server locally 2022-06-15 18:26:58 +01:00
types
ui ui: Fix intl keys in order to render correct messages for empty states (#13409) 2022-06-16 12:07:04 +01:00
version Change default dates 2022-06-09 17:07:41 -07:00
website removed most of 'ECS service' information 2022-06-21 17:02:18 -07:00
.dockerignore
.gitattributes
.gitignore
.golangci.yml
CHANGELOG.md Add latest changelog entries (#13363) 2022-06-06 11:52:13 -07:00
Dockerfile
GNUmakefile Cleanup and extend basic build date 2022-06-09 17:04:05 -07:00
LICENSE
NOTICE.md
README.md
Vagrantfile
fixup_acl_move.sh
go.mod Update go-grpc/grpc to resolve conection memory leak 2022-06-08 11:29:29 +01:00
go.sum Update go-grpc/grpc to resolve conection memory leak 2022-06-08 11:29:29 +01:00
main.go

README.md

Consul logo Consul

Docker Pulls Go Report Card

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, macOS, FreeBSD, Solaris, and Windows and includes an optional browser based UI. 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. For contributions specifically to the browser based UI, please refer to the UI's README.md for guidance.