Release/1.17.x #19950
Closed
Release/1.17.x #19950
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Upgrade Consul UI to Node 18 (#19252) * Upgrading node to node 18 * Ensure we're on latest version of yarn as well * add comma to make frontend tests run * Use Node 18 Alpine image in UI build dockerfile * delete package-lock.json --------- Co-authored-by: wenincode <[email protected]> Co-authored-by: Ella Cai <[email protected]> Co-authored-by: Ella Cai <[email protected]> * Resetting node 14 on nightly test 1.13 --------- Co-authored-by: Chris Hut <[email protected]> Co-authored-by: Ella Cai <[email protected]> Co-authored-by: Ella Cai <[email protected]>
…pulated for gRPC into release/1.17.x (#19366) * backport of commit 0a8fe0d * backport of commit 74bf2aa --------- Co-authored-by: Michael Zalimeni <[email protected]>
….17.x (#19368) * backport of commit dba8d67 * backport of commit 436cc19 --------- Co-authored-by: Chris S. Kim <[email protected]>
…o release/1.17.x (#19371) backport of commit aeb0b22 Co-authored-by: Ronald Ekambi <[email protected]>
… non compatible service name) into release/1.17.x (#19380) * backport of commit 880d151 * backport of commit 7fedfba --------- Co-authored-by: David Yu <[email protected]>
#19387) * backport of commit b9249e2 * backport of commit 93341a6 --------- Co-authored-by: Chris S. Kim <[email protected]>
…multaneously into release/1.17.x (#19390) backport of commit 2c5af2f Co-authored-by: Ronald Ekambi <[email protected]>
* Update dns-configuration.mdx
…ase/1.17.x (#19396) * backport of commit e9eabcb * backport of commit 013de0b --------- Co-authored-by: Andrew Stucki <[email protected]>
…9408) backport of commit 2da2736 Co-authored-by: Nathan Coleman <[email protected]>
backport of commit 4804558 Co-authored-by: Chris S. Kim <[email protected]>
…v2 changes into release/1.17.x (#19416) backport of commit fa50df4 Co-authored-by: John Murret <[email protected]>
CVE-2023-44487) to release/1.17.x (#19417) Bump google.golang.org/grpc to 1.56.3 This resolves [CVE-2023-44487](https://nvd.nist.gov/vuln/detail/CVE-2023-44487). Co-authored-by: Chris Thain <[email protected]>
…ta.name into release/1.17.x (#19434) backport of commit e9006e6 Co-authored-by: Tu Nguyen <[email protected]>
* backport of commit 2290dba * backport of commit 6058722 --------- Co-authored-by: David Yu <[email protected]>
…se/1.17.x (#19448) backport of commit 431bbb9 Co-authored-by: Nathan Coleman <[email protected]>
…ane requirements into release/1.17.x (#19452) * backport of commit a10c94d * backport of commit 91ab4ec --------- Co-authored-by: Nathan Coleman <[email protected]>
…#19466) backport of commit 21f193c Co-authored-by: trujillo-adam <[email protected]>
…e/1.17.x (#19471) backport of commit 81c9697 Co-authored-by: jm96441n <[email protected]>
backport of commit d399654 Co-authored-by: Semir Patel <[email protected]>
… of going directly to the docker hub into release/1.17.x (#19486) backport of commit 5ab1e98 Co-authored-by: R.B. Boyer <[email protected]>
…1.17.x (#19488) backport of commit 3ed40f6 Co-authored-by: skpratt <[email protected]>
…ructs when requested into release/1.17.x (#19492) 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 Co-authored-by: R.B. Boyer <[email protected]>
… release/1.17.x (#19494) 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. Co-authored-by: R.B. Boyer <[email protected]>
backport of commit 52a0072 Co-authored-by: Nitya Dhanushkodi <[email protected]>
…testing files into release/1.17.x (#19507) chore: apply enterprise changes that were missed to some testing files (#19504) This should align between CE ef35525 and ENT 7f95226dbe40151c8f17dd4464784b60cf358dc1 in: - testing/integration/consul-container - test-integ - testing/deployer Co-authored-by: R.B. Boyer <[email protected]>
… into release/1.17.x (#19510) backport of commit ebc913f Co-authored-by: R.B. Boyer <[email protected]>
Generate helm docs from 1.3.5 of consul-k8s release
chore: disable CRT for inactive release
manual backport of pr 21251 to release 1.17.x
…ons required in other submodules into release/1.17.x (#21639) add build support script to print out the submodule versions required in other submodules (#21635) * add build support script to print out the submodule versions required in other submodules * update help and usage. exclude current submodule in output.
pull over Validate_Clusters to api package
…21648) * api/v1.27.1 * envoyextensions/v0.5.3 * updating go.mod in root.
* api/v1.27.2 * restore replace statements in api after api module was published. * envoyextensions/v0.5.4 * troubleshoot/v0.5.4 * updating rootgo.mod
…release/1.17.x (#21669) run integration tests on push in main and release/* (#21666) * run integration tests on push in main and release/* * Update .github/workflows/test-integrations.yml --------- Co-authored-by: Michael Zalimeni <[email protected]>
* update changelog to include 1.17.7 * update version * Apply suggestions from code review Co-authored-by: Michael Zalimeni <[email protected]> --------- Co-authored-by: Michael Zalimeni <[email protected]>
update helm docs
|
This pull request has been automatically flagged for inactivity because it has not been acted upon in the last 60 days. It will be closed if no new activity occurs in the next 30 days. Please feel free to re-open to resurrect the change if you feel this has happened by mistake. Thank you for your contributions. |
github-actions
bot
added
the
meta/stale
|
Closing due to inactivity. If you feel this was a mistake or you wish to re-open at any time in the future, please leave a comment and it will be re-surfaced for the maintainers to review. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Testing & Reproduction steps
Links
PR Checklist