Skip to content

Backport of testing/deployer: update deployer to use v2 catalog constructs when requested into release/1.17.x#19492

Merged
hc-github-team-consul-core merged 1 commit into
release/1.17.xfrom
backport/rboyer/deployer-catalog-v2/typically-handy-seasnail
Nov 2, 2023
Merged

Backport of testing/deployer: update deployer to use v2 catalog constructs when requested into release/1.17.x#19492
hc-github-team-consul-core merged 1 commit into
release/1.17.xfrom
backport/rboyer/deployer-catalog-v2/typically-handy-seasnail

Conversation

@hc-github-team-consul-core
Copy link
Copy Markdown
Collaborator

Backport

This PR is auto-generated from #19046 to be assessed for backporting due to the inclusion of the label backport/1.17.

The below text is copied from the body of the original PR.


Description

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

NET-5734


Overview of commits

@hc-github-team-consul-core hc-github-team-consul-core requested a review from a team as a code owner November 2, 2023 19:28
@hc-github-team-consul-core hc-github-team-consul-core requested a review from a team November 2, 2023 19:28
@hc-github-team-consul-core hc-github-team-consul-core requested review from dekimsey and randyhdev and removed request for a team November 2, 2023 19:28
@hc-github-team-consul-core hc-github-team-consul-core force-pushed the backport/rboyer/deployer-catalog-v2/typically-handy-seasnail branch 2 times, most recently from a8ff8ec to 6ef72fd Compare November 2, 2023 19:28
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Auto approved Consul Bot automated PR

@github-actions github-actions Bot added type/docs Documentation needs to be created/updated/clarified theme/api Relating to the HTTP API interface theme/acls ACL and token generation theme/cli Flags and documentation for the CLI interface theme/config Relating to Consul Agent configuration, including reloading theme/ui Anything related to the UI theme/connect Anything related to Consul Connect, Service Mesh, Side Car Proxies type/ci Relating to continuous integration (CI) tooling for testing or releases pr/dependencies PR specifically updates dependencies of project theme/envoy/xds Related to Envoy support theme/contributing Additions and enhancements to community contributing materials labels Nov 2, 2023
…equested (#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
@rboyer rboyer force-pushed the backport/rboyer/deployer-catalog-v2/typically-handy-seasnail branch from 6ef72fd to 2779a2e Compare November 2, 2023 19:35
@hc-github-team-consul-core hc-github-team-consul-core merged commit 2b4d96a into release/1.17.x Nov 2, 2023
@hc-github-team-consul-core hc-github-team-consul-core deleted the backport/rboyer/deployer-catalog-v2/typically-handy-seasnail branch November 2, 2023 19:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

pr/dependencies PR specifically updates dependencies of project theme/acls ACL and token generation theme/api Relating to the HTTP API interface theme/cli Flags and documentation for the CLI interface theme/config Relating to Consul Agent configuration, including reloading theme/connect Anything related to Consul Connect, Service Mesh, Side Car Proxies theme/contributing Additions and enhancements to community contributing materials theme/envoy/xds Related to Envoy support theme/ui Anything related to the UI type/ci Relating to continuous integration (CI) tooling for testing or releases type/docs Documentation needs to be created/updated/clarified

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants