consul

Commit Graph

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	235747d473	deployer: add a bunch of test coverage and fix a few panics (#20694 ) This adds a bunch of coverage of the topology.Compile method. It is not complete, but it is a start. - A few panics and miscellany were fixed. - The testing/deployer tests are now also run in CI.	9 months ago
Nitya Dhanushkodi	92aab7ea31	[NET-5586][rebased] v2: Support virtual port references in config (#20371 ) [OG Author: michael.zalimeni@hashicorp.com, rebase needed a separate PR] * v2: support virtual port in Service port references In addition to Service target port references, allow users to specify a port by stringified virtual port value. This is useful in environments such as Kubernetes where typical configuration is written in terms of Service virtual ports rather than workload (pod) target port names. Retaining the option of referencing target ports by name supports VMs, Nomad, and other use cases where virtual ports are not used by default. To support both uses cases at once, we will strictly interpret port references based on whether the value is numeric. See updated `ServicePort` docs for more details. * v2: update service ref docs for virtual port support Update proto and generated .go files with docs reflecting virtual port reference support. * v2: add virtual port references to L7 topo test Add coverage for mixed virtual and target port references to existing test. * update failover policy controller tests to work with computed failover policy and assert error conditions against FailoverPolicy and ComputedFailoverPolicy resources * accumulate services; don't overwrite them in enterprise --------- Co-authored-by: Michael Zalimeni <michael.zalimeni@hashicorp.com> Co-authored-by: R.B. Boyer <rb@hashicorp.com>	10 months ago
cskh	748458a07b	upgrade test (LTS): utility functions to support ent users (#20186 ) * upgrade test (LTS): utility functions to support ent users * go mod tidy * add comment	11 months ago
cskh	8e2d4e3aaf	upgrade test(LTS): import remaining agent config from usage profile (#19999 ) * upgrade test(LTS): import remaining agent config from usage profile	11 months ago
cskh	33a90edfab	Upgrade test(LTS): use network area to federate cluster (#19934 ) - Join areas - wait for members alive and validate cross area service discovery	12 months ago
cskh	0ca070b301	upgrade test(LTS): add segments to version 1.10 (#19861 )	12 months ago
Semir Patel	2d1f308138	resource: add v2tenancy feature flag to deployer tests (#19774 )	1 year ago
cskh	04a3a3e8d0	Integ test (test/deployer): upgrade test with service mesh (#19658 ) * Integ test (test/deployer): upgrade test with service mesh * license	1 year 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	a7f3069a94	test: add a v2 container integration test of xRoute splits (#19570 ) This adds a deployer-based integration test verifying that a 90/10 traffic split works for: HTTPRoute, GRPCRoute, and TCPRoute.	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
cskh	4b26ed8eba	integ test: snapshot mesh frozen bug test (#19435 ) * integ test: snapshot mesh frozen bug test	1 year ago
Nick Irvine	373c7dc144	switch all client nodes in dc2 to dataplane [NET-4299] (#18608 )	1 year ago
hashicorp-copywrite[bot]	5fb9df1640	[COMPLIANCE] License changes (#18443 ) * Adding explicit MPL license for sub-package This directory and its subdirectories (packages) contain files licensed with the MPLv2 `LICENSE` file in this directory and are intentionally licensed separately from the BSL `LICENSE` file at the root of this repository. * Adding explicit MPL license for sub-package This directory and its subdirectories (packages) contain files licensed with the MPLv2 `LICENSE` file in this directory and are intentionally licensed separately from the BSL `LICENSE` file at the root of this repository. * Updating the license from MPL to Business Source License Going forward, this project will be licensed under the Business Source License v1.1. Please see our blog post for more details at <Blog URL>, FAQ at www.hashicorp.com/licensing-faq, and details of the license at www.hashicorp.com/bsl. * add missing license headers * Update copyright file headers to BUSL-1.1 * Update copyright file headers to BUSL-1.1 * Update copyright file headers to BUSL-1.1 * Update copyright file headers to BUSL-1.1 * Update copyright file headers to BUSL-1.1 * Update copyright file headers to BUSL-1.1 * Update copyright file headers to BUSL-1.1 * Update copyright file headers to BUSL-1.1 * Update copyright file headers to BUSL-1.1 * Update copyright file headers to BUSL-1.1 * Update copyright file headers to BUSL-1.1 * Update copyright file headers to BUSL-1.1 * Update copyright file headers to BUSL-1.1 * Update copyright file headers to BUSL-1.1 * Update copyright file headers to BUSL-1.1 --------- Co-authored-by: hashicorp-copywrite[bot] <110428419+hashicorp-copywrite[bot]@users.noreply.github.com>	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

17 Commits (f76da16000bebce8cdb112c17107b05de81eec97)