Go to file
R.B. Boyer bc10055edc
peering: replicate expected SNI, SPIFFE, and service protocol to peers (#13218)
The importing peer will need to know what SNI and SPIFFE name
corresponds to each exported service. Additionally it will need to know
at a high level the protocol in use (L4/L7) to generate the appropriate
connection pool and local metrics.

For replicated connect synthetic entities we edit the `Connect{}` part
of a `NodeService` to have a new section:

    {
      "PeerMeta": {
        "SNI": [
          "web.default.default.owt.external.183150d5-1033-3672-c426-c29205a576b8.consul"
        ],
        "SpiffeID": [
          "spiffe://183150d5-1033-3672-c426-c29205a576b8.consul/ns/default/dc/dc1/svc/web"
        ],
        "Protocol": "tcp"
      }
    }

This data is then replicated and saved as-is at the importing side. Both
SNI and SpiffeID are slices for now until I can be sure we don't need
them for how mesh gateways will ultimately work.
2022-05-25 12:37:44 -05:00
.changelog Merge pull request #13143 from hashicorp/envoy-connection-limit 2022-05-25 07:48:50 -07:00
.circleci build: wire up remaining 5 helper tools into the same auto-install logic used for protobuf tools (#13184) 2022-05-23 10:50:45 -05:00
.github [CI-only] Update tagging for dev_tags (#13199) 2022-05-24 15:23:01 -07:00
.release [CI-only] Build and publish dev dockerhub images (#13084) 2022-05-17 12:23:03 -07:00
acl [OSS] Add upsert handling for receiving CheckServiceNode (#13061) 2022-05-12 15:04:44 -06:00
agent peering: replicate expected SNI, SPIFFE, and service protocol to peers (#13218) 2022-05-25 12:37:44 -05:00
api chore(test): Update bats version 2022-05-24 11:56:08 -04:00
bench Gets benchmarks running again and does a rough pass for 0.7.1. 2016-11-29 13:02:26 -08:00
build-support Add connection limit setting to service defaults 2022-05-24 10:13:38 -07:00
command chore(test): Update bats version 2022-05-24 11:56:08 -04:00
connect Retry on bad dogstatsd connection (#13091) 2022-05-19 16:03:46 -04:00
contributing Move contributing to docs 2021-08-30 16:17:09 -04:00
docs Add some docs on pprof usage (#12551) 2022-05-09 14:15:21 -06:00
grafana add readme outlining how to edit and publish 2021-01-12 14:47:11 -08:00
internal internal: port RPC glue changes from Enterprise (#13034) 2022-05-11 15:03:07 -07:00
ipaddr Ensure Consul is IPv6 compliant (#5468) 2019-06-04 10:02:38 -04:00
lib telemetry: remove unused arg (#13161) 2022-05-19 19:17:30 -07:00
logging peering: initial sync (#12842) 2022-04-21 17:34:40 -05:00
proto peering: replicate expected SNI, SPIFFE, and service protocol to peers (#13218) 2022-05-25 12:37:44 -05:00
proto-public Specify go_package explicitly 2022-05-24 10:22:53 -07:00
sdk add general runstep test helper instead of copying it all over the place (#13013) 2022-05-10 15:25:51 -05:00
sentinel re-run gofmt on 1.17 (#11579) 2021-11-16 12:04:01 -06:00
service_os re-run gofmt on 1.17 (#11579) 2021-11-16 12:04:01 -06:00
snapshot Vendor in rpc mono repo for net/rpc fork, go-msgpack, msgpackrpc. (#12311) 2022-02-14 09:45:45 -08:00
test chore(test): Update bats version 2022-05-24 11:56:08 -04:00
testrpc peering: initial sync (#12842) 2022-04-21 17:34:40 -05:00
tlsutil Update go version to 1.18.1 2022-04-18 11:41:10 -04:00
types agent: convert listener config to TLS types (#12522) 2022-03-24 15:32:25 -04:00
ui ui: Icon related fixups (#13183) 2022-05-25 14:28:42 +01:00
version update main to reflect 1.13.0-dev (#13192) 2022-05-25 09:06:36 -07:00
website docs: Update service/node identities text on ACL index (#13022) 2022-05-18 18:55:35 -07:00
.dockerignore Update the scripting 2018-06-14 21:42:47 -04:00
.gitattributes Initial commit 2013-11-04 14:15:27 -08:00
.gitignore changelog: snapshot-agent acl token fix for CLI and ENV 2022-04-25 16:46:55 -04:00
.golangci.yml Fix proto lint errors after version bump 2022-05-24 18:44:54 -07:00
CHANGELOG.md Update CHANGELOG to mention removal of Envoy 1.17.4 and 1.18.6 (#13207) 2022-05-25 08:57:01 -07:00
Dockerfile Update docker image base to alpine:3.15 (#12276) 2022-02-04 13:56:39 -08:00
GNUmakefile build: re-add proto-tools dep to make proto (#13223) 2022-05-25 12:24:55 -05:00
LICENSE Initial commit 2013-11-04 14:15:27 -08:00
NOTICE.md add copyright notice file 2018-07-09 10:58:26 -07:00
README.md Adjust README header to work in light and dark modes 2022-02-07 16:46:46 -08:00
Vagrantfile Adds a basic Linux Vagrant setup, stolen from Nomad. 2017-10-06 08:10:12 -07:00
fixup_acl_move.sh Fixup script 2 2022-04-05 14:52:43 -07:00
go.mod Add connection limit setting to service defaults 2022-05-24 10:13:38 -07:00
go.sum Add connection limit setting to service defaults 2022-05-24 10:13:38 -07:00
main.go cmd: introduce a shim to expose Stdout/Stderr writers 2021-06-02 16:51:34 -04:00

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.