bc10055edc
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.
|
||
|---|---|---|
| .. | ||
| health_snapshot.go | ||
| health_snapshot_test.go | ||
| replication.go | ||
| service.go | ||
| service_oss_test.go | ||
| service_test.go | ||
| stream_test.go | ||
| stream_tracker.go | ||
| stream_tracker_test.go | ||
| subscription_blocking.go | ||
| subscription_manager.go | ||
| subscription_manager_test.go | ||
| subscription_state.go | ||
| subscription_state_test.go | ||
| subscription_view.go | ||
| subscription_view_test.go | ||
| testing.go | ||
| testutil_oss_test.go | ||
| validate.go | ||
| validate_test.go | ||