consul

Commit Graph

Author	SHA1	Message	Date
R.B. Boyer	424f3cdd2c	proxycfg: introduce explicit UpstreamID in lieu of bare string (#12125 ) The gist here is that now we use a value-type struct proxycfg.UpstreamID as the map key in ConfigSnapshot maps where we used to use "upstream id-ish" strings. These are internal only and used just for bidirectional trips through the agent cache keyspace (like the discovery chain target struct). For the few places where the upstream id needs to be projected into xDS, that's what (proxycfg.UpstreamID).EnvoyID() is for. This lets us ALWAYS inject the partition and namespace into these things without making stuff like the golden testdata diverge.	2022-01-20 10:12:04 -06:00
freddygv	2fe27b748d	Check ingress upstreams when gating chain watches	2021-12-13 18:56:28 -07:00
freddygv	0e507492d0	Update proxycfg for ingress service partitions	2021-11-12 14:33:31 -07:00
Paul Banks	78a00f2e1c	Add support for enabling connect-based ingress TLS per listener.	2021-10-19 20:58:28 +01:00
Paul Banks	20d0bf81f7	Revert abandonned changes to proxycfg for Ent test consistency	2021-09-23 10:13:19 +01:00
Paul Banks	659321d008	Handle namespaces in route names correctly; add tests for enterprise	2021-09-23 10:09:11 +01:00
Paul Banks	ccbda0c285	Update proxycfg to hold more ingress config state	2021-09-23 10:08:02 +01:00
Paul Banks	f439dfc04f	Ingress gateway header manip plumbing	2021-09-10 21:09:24 +01:00
Dhia Ayachi	1950ebbe1f	oss portion of ent #1069 (#10883 )	2021-08-20 12:57:45 -04:00
Daniel Nephin	6bc5255028	proxycfg: move each handler into a seprate file There is no interaction between these handlers, so splitting them into separate files makes it easier to discover the full implementation of each kindHandler.	2021-06-21 15:48:40 -04:00

10 Commits