Upgrade Consul client to v1.27 (VPS-10853) #86
Merged
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
jessekempf-vsco
force-pushed
the
VPS-10853
branch
from
347bb72
to
7595a22
Compare
negator
reviewed
Jan 29, 2024
jessekempf-vsco
force-pushed
the
VPS-10853
branch
2 times, most recently
from
dd939eb
to
d7f7d42
Compare
jessekempf-vsco
force-pushed
the
VPS-10853
branch
from
d7f7d42
to
cc419d3
Compare
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.
We need dcdr to work with recent versions of Consul so that VSCO can perform its internal Kubernetes upgrade.
The primary change is to update the consul package from v0.6.5 to v1.27.0, and it entailed a secondary change of updating Go to v1.18 from v1.14.