* api/v1.28.4
* envoyextensions/v0.6.2
* troubleshoot/v0.6.4
* updating go.mod in root.
* fix lint error in test
* fix versions of sdk to be 0.16.0 which is the max for the 1.18.x long lived branch
* fix envoyproxy
Backport of security: bump go, x/net and envoy versions into release/1.18.x
* Bump go version
* Bump x/net
* Bump envoy version
* Add changelog
---------
Co-authored-by: Michael Zalimeni <michael.zalimeni@hashicorp.com>
* add build tags/import k8s specific proto packages
* fix generated import paths
* fix gomod linting issue
* mod tidy every go mod file
* revert protobuff version, take care of in different pr
* cleaned up new lines
* added newline to end of file
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
John Murret