consul/lib
R.B. Boyer 6adad71125
wan federation via mesh gateways (#6884)
This is like a Möbius strip of code due to the fact that low-level components (serf/memberlist) are connected to high-level components (the catalog and mesh-gateways) in a twisty maze of references which make it hard to dive into. With that in mind here's a high level summary of what you'll find in the patch:

There are several distinct chunks of code that are affected:

* new flags and config options for the server

* retry join WAN is slightly different

* retry join code is shared to discover primary mesh gateways from secondary datacenters

* because retry join logic runs in the *agent* and the results of that
  operation for primary mesh gateways are needed in the *server* there are
  some methods like `RefreshPrimaryGatewayFallbackAddresses` that must occur
  at multiple layers of abstraction just to pass the data down to the right
  layer.

* new cache type `FederationStateListMeshGatewaysName` for use in `proxycfg/xds` layers

* the function signature for RPC dialing picked up a new required field (the
  node name of the destination)

* several new RPCs for manipulating a FederationState object:
  `FederationState:{Apply,Get,List,ListMeshGateways}`

* 3 read-only internal APIs for debugging use to invoke those RPCs from curl

* raft and fsm changes to persist these FederationStates

* replication for FederationStates as they are canonically stored in the
  Primary and replicated to the Secondaries.

* a special derivative of anti-entropy that runs in secondaries to snapshot
  their local mesh gateway `CheckServiceNodes` and sync them into their upstream
  FederationState in the primary (this works in conjunction with the
  replication to distribute addresses for all mesh gateways in all DCs to all
  other DCs)

* a "gateway locator" convenience object to make use of this data to choose
  the addresses of gateways to use for any given RPC or gossip operation to a
  remote DC. This gets data from the "retry join" logic in the agent and also
  directly calls into the FSM.

* RPC (`:8300`) on the server sniffs the first byte of a new connection to
  determine if it's actually doing native TLS. If so it checks the ALPN header
  for protocol determination (just like how the existing system uses the
  type-byte marker).

* 2 new kinds of protocols are exclusively decoded via this native TLS
  mechanism: one for ferrying "packet" operations (udp-like) from the gossip
  layer and one for "stream" operations (tcp-like). The packet operations
  re-use sockets (using length-prefixing) to cut down on TLS re-negotiation
  overhead.

* the server instances specially wrap the `memberlist.NetTransport` when running
  with gateway federation enabled (in a `wanfed.Transport`). The general gist is
  that if it tries to dial a node in the SAME datacenter (deduced by looking
  at the suffix of the node name) there is no change. If dialing a DIFFERENT
  datacenter it is wrapped up in a TLS+ALPN blob and sent through some mesh
  gateways to eventually end up in a server's :8300 port.

* a new flag when launching a mesh gateway via `consul connect envoy` to
  indicate that the servers are to be exposed. This sets a special service
  meta when registering the gateway into the catalog.

* `proxycfg/xds` notice this metadata blob to activate additional watches for
  the FederationState objects as well as the location of all of the consul
  servers in that datacenter.

* `xds:` if the extra metadata is in place additional clusters are defined in a
  DC to bulk sink all traffic to another DC's gateways. For the current
  datacenter we listen on a wildcard name (`server.<dc>.consul`) that load
  balances all servers as well as one mini-cluster per node
  (`<node>.server.<dc>.consul`)

* the `consul tls cert create` command got a new flag (`-node`) to help create
  an additional SAN in certs that can be used with this flavor of federation.
2020-03-09 15:59:02 -05:00
..
file cli: improve the file safety of 'consul tls' subcommands (#7186) 2020-01-31 10:12:36 -06:00
semaphore connect: tame thundering herd of CSRs on CA rotation (#5228) 2019-01-22 17:19:36 +00:00
cluster.go
cluster_test.go
eof.go
json.go Add Namespace support to the API module and the CLI commands (#6874) 2019-12-06 11:14:56 -05:00
map_walker.go Allow MapWalk to handle []interface{} elements that are []uint8 (#5800) 2019-05-07 11:40:48 -04:00
map_walker_test.go Allow MapWalk to handle []interface{} elements that are []uint8 (#5800) 2019-05-07 11:40:48 -04:00
math.go
math_test.go
patch_hcl.go Make PatchSliceOfMaps case insensitive 2020-01-31 09:56:02 -05:00
patch_hcl_test.go Make PatchSliceOfMaps case insensitive 2020-01-31 09:56:02 -05:00
path.go
rand.go
retry.go Implement config entry replication (#5706) 2019-04-26 13:38:39 -04:00
retry_test.go Implement config entry replication (#5706) 2019-04-26 13:38:39 -04:00
rtt.go
rtt_test.go
serf.go agent: fewer file local differences between enterprise and oss (#6820) (#6898) 2019-12-06 21:35:58 +01:00
slice.go wan federation via mesh gateways (#6884) 2020-03-09 15:59:02 -05:00
slice_test.go wan federation via mesh gateways (#6884) 2020-03-09 15:59:02 -05:00
stop_context.go fix typos reported by golangci-lint:misspell (#5434) 2019-03-06 11:13:28 -06:00
string.go
string_test.go
telemetry.go Simplified code in various places (#6176) 2019-07-20 09:37:19 -04:00
telemetry_test.go Refactor to use embedded struct. 2018-06-25 12:25:39 -07:00
translate.go connect: remove managed proxies (#6220) 2019-08-09 15:19:30 -04:00
translate_test.go Make a few config entry endpoints return 404s and allow for snake_case and lowercase key names. (#5748) 2019-04-30 18:19:19 -04:00
useragent.go Add a helper for generating Consul's user-agent string 2018-05-25 15:50:18 -04:00
useragent_test.go Add a helper for generating Consul's user-agent string 2018-05-25 15:50:18 -04:00
uuid.go New ACLs (#4791) 2018-10-19 12:04:07 -04:00