consul

History

R.B. Boyer 2317f37b4d state: prohibit exported discovery chains to have cross-datacenter or cross-partition references (#13726 ) Because peerings are pairwise, between two tuples of (datacenter, partition) having any exported reference via a discovery chain that crosses out of the peered datacenter or partition will ultimately not be able to work for various reasons. The biggest one is that there is no way in the ultimate destination to configure an intention that can allow an external SpiffeID to access a service. This PR ensures that a user simply cannot do this, so they won't run into weird situations like this.		2 years ago
..
connect-proxy-exported-to-peers.latest.golden	…
connect-proxy-with-chain-and-failover.latest.golden	…
connect-proxy-with-chain-and-overrides.latest.golden	…
connect-proxy-with-chain-external-sni.latest.golden	…
connect-proxy-with-chain.latest.golden	…
connect-proxy-with-default-chain-and-custom-cluster.latest.golden	…
connect-proxy-with-peered-upstreams.latest.golden	…
connect-proxy-with-tcp-chain-double-failover-through-local-gateway-triggered.latest.golden	…
connect-proxy-with-tcp-chain-double-failover-through-local-gateway.latest.golden	…
connect-proxy-with-tcp-chain-double-failover-through-remote-gateway-triggered.latest.golden	…
connect-proxy-with-tcp-chain-double-failover-through-remote-gateway.latest.golden	…
connect-proxy-with-tcp-chain-failover-through-local-gateway-triggered.latest.golden	…
connect-proxy-with-tcp-chain-failover-through-local-gateway.latest.golden	…
connect-proxy-with-tcp-chain-failover-through-remote-gateway-triggered.latest.golden	…
connect-proxy-with-tcp-chain-failover-through-remote-gateway.latest.golden	…
defaults.latest.golden	…
ingress-gateway-no-services.latest.golden	…
ingress-gateway.latest.golden	…
ingress-multiple-listeners-duplicate-service.latest.golden	…
ingress-splitter-with-resolver-redirect.latest.golden	…
ingress-with-chain-and-failover.latest.golden	…
ingress-with-chain-external-sni.latest.golden	…
ingress-with-chain.latest.golden	…
ingress-with-tcp-chain-double-failover-through-local-gateway-triggered.latest.golden	…
ingress-with-tcp-chain-double-failover-through-local-gateway.latest.golden	…
ingress-with-tcp-chain-double-failover-through-remote-gateway-triggered.latest.golden	…
ingress-with-tcp-chain-double-failover-through-remote-gateway.latest.golden	…
ingress-with-tcp-chain-failover-through-local-gateway-triggered.latest.golden	…
ingress-with-tcp-chain-failover-through-local-gateway.latest.golden	…
ingress-with-tcp-chain-failover-through-remote-gateway-triggered.latest.golden	…
ingress-with-tcp-chain-failover-through-remote-gateway.latest.golden	…
mesh-gateway-default-service-subset.latest.golden	…
mesh-gateway-newer-information-in-federation-states.latest.golden	…
mesh-gateway-no-services.latest.golden	…
mesh-gateway-older-information-in-federation-states.latest.golden	…
mesh-gateway-service-subsets.latest.golden	…
mesh-gateway-using-federation-states.latest.golden	…
mesh-gateway-with-exported-peered-services-http-with-router.latest.golden	state: prohibit exported discovery chains to have cross-datacenter or cross-partition references (#13726 )	2 years ago
mesh-gateway-with-exported-peered-services-http.latest.golden	xds: mesh gateways now correctly load up peer-exported discovery chains using L7 protocols (#13624 )	2 years ago
mesh-gateway-with-exported-peered-services.latest.golden	xds: mesh gateways now correctly load up peer-exported discovery chains using L7 protocols (#13624 )	2 years ago
mesh-gateway.latest.golden	…
splitter-with-resolver-redirect.latest.golden	…
terminating-gateway-default-service-subset.latest.golden	…
terminating-gateway-no-services.latest.golden	…
terminating-gateway-service-subsets.latest.golden	…
terminating-gateway.latest.golden	…