7 Commits (32ce33825d8aca30d1259aef0563113985461c46)

Author	SHA1	Message	Date
R.B. Boyer	50b26aa56a	deployer: remove catalog/mesh v2 support (#21194) ... - Low level plumbing for resources is still retained for now. - Retain "Workload" terminology over "Service". - Revert "Destination" terminology back to "Upstream". - Remove TPROXY support as it only worked for v2.	6 months ago
R.B. Boyer	8bea6cd82a	deployer: ensure the proxy/dns/pause containers do not continually get replaced due to a change in a docker default (#21043)	7 months ago
R.B. Boyer	b2979f6edf	testing/deployer: rename various terms to better align with v2 and avoid confusion (#19600) ... Conceptually renaming the following topology terms to avoid confusion with v2 and to better align with it: - ServiceID -> ID - Service -> Workload - Upstream -> Destination	1 year ago
R.B. Boyer	4b85aa5a97	testing/deployer: support tproxy in v2 for dataplane (#19094) ... This updates the testing/deployer (aka "topology test") framework to allow for a v2-oriented topology to opt services into enabling TransparentProxy. The restrictions are similar to that of #19046 The multiport Ports map that was added in #19046 was changed to allow for the protocol to be specified at this time, but for now the only supported protocol is TCP as only L4 functions currently on main. As part of making transparent proxy work, the DNS server needed a new zonefile for responding to virtual.consul requests, since there is no Kubernetes DNS and the Consul DNS work for v2 has not happened yet. Once Consul DNS supports v2 we should switch over. For now the format of queries is: <service>--<namespace>--<partition>.virtual.consul Additionally: - All transparent proxy enabled services are assigned a virtual ip in the 10.244.0/24 range. This is something Consul will do in v2 at a later date, likely during 1.18. - All services with exposed ports (non-mesh) are assigned a virtual port number for use with tproxy - The consul-dataplane image has been made un-distroless, and gotten the necessary tools to execute consul connect redirect-traffic before running dataplane, thus simulating a kubernetes init container in plain docker.	1 year ago
R.B. Boyer	a72f868218	testing/deployer: update deployer to use v2 catalog constructs when requested (#19046) ... This updates the testing/deployer (aka "topology test") framework to conditionally configure and launch catalog constructs using v2 resources. This is controlled via a Version field on the Node construct in a topology.Config. This only functions for a dataplane type and has other restrictions that match the rest of v2 (no peering, no wanfed, no mesh gateways). Like config entries, you can statically provide a set of initial resources to be synced when bringing up the cluster (beyond those that are generated for you such as workloads, services, etc). If you want to author a test that can be freely converted between v1 and v2 then that is possible. If you switch to the multi-port definition on a topology.Service (aka "workload/instance") then that makes v1 ineligible. This also adds a starter set of "on every PR" integration tests for single and multiport under test-integ/catalogv2	1 year ago
Nick Irvine	373c7dc144	switch all client nodes in dc2 to dataplane [NET-4299] (#18608)	1 year ago
Nick Irvine	62005369b5	Add `testing/deployer` (neé `consul-topology`) [NET-4610] (#17823) ... Co-authored-by: R.B. Boyer <4903+rboyer@users.noreply.github.com> Co-authored-by: R.B. Boyer <rb@hashicorp.com> Co-authored-by: Freddy <freddygv@users.noreply.github.com>	1 year ago