Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Envoy compatibility matrices to include consul 1.20.x and dataplane 1.6.x #21852

Merged
merged 4 commits into from
Oct 17, 2024

Conversation

nathancoleman
Copy link
Member

Description

Update Envoy matrices to include latest set of releases for consul + consul-dataplane

Testing & Reproduction steps

Links

PR Checklist

  • updated test coverage
  • external facing docs updated
  • appropriate backport labels added
  • not a security concern

@nathancoleman nathancoleman added pr/no-changelog PR does not need a corresponding .changelog entry backport/1.20 Changes are backported to 1.20 labels Oct 17, 2024
@github-actions github-actions bot added the type/docs Documentation needs to be created/updated/clarified label Oct 17, 2024
Copy link
Member Author

@nathancoleman nathancoleman left a comment

Choose a reason for hiding this comment

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

Personal review

@@ -122,7 +123,6 @@ until the LTS release reaches its end of maintenance.

| Consul Version | Default `consul-dataplane` Version | Other compatible `consul-dataplane` Versions |
| -------------- | -------------------------------------|----------------------------------------------|
| 1.19.x Ent | 1.5.x (Envoy 1.29.x) | 1.4.x (Envoy 1.28.x) |
Copy link
Member Author

Choose a reason for hiding this comment

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

I'm not sure why 1.19 was included in this table of LTS releases, but I removed it

Copy link
Member

Choose a reason for hiding this comment

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

🍝

Comment on lines +111 to 112
| 1.20.x CE | 1.6.x (Envoy 1.31.x) | 1.5.x (Envoy 1.29.x) |
| 1.19.x CE | 1.5.x (Envoy 1.29.x) | 1.4.x (Envoy 1.28.x) |
Copy link
Member Author

Choose a reason for hiding this comment

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

Interestingly, 1.20.x includes Envoy 1.31.x (link) while 1.19.x never made it to 1.30.x and stayed at 1.29.x (link), but this table reflects current reality

Copy link
Member

Choose a reason for hiding this comment

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

We had to jump two versions at some point bc we'd started to lag >1 release on latest Envoy vs. latest Consul due to release cadence differences. 1.20 happened to be selected as the version for the jump.

@nathancoleman nathancoleman marked this pull request as ready for review October 17, 2024 20:57
@nathancoleman nathancoleman requested a review from a team as a code owner October 17, 2024 20:57
Comment on lines -139 to -140
| 1.5.0 - 1.5.latest | 1.18.x Ent | Envoy 1.29.x |
| 1.4.0 - 1.4.latest | 1.18.x Ent | Envoy 1.28.x |
Copy link
Member Author

Choose a reason for hiding this comment

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

I've removed these as neither dataplane release spans multiple major Envoy versions, which is what this section of the doc is meant to be

Comment on lines -141 to -142
| 1.2.0 - 1.2.latest | 1.18.x Ent | Envoy 1.27.x |
| 1.2.0 - 1.2.7 | 1.18.x Ent | Envoy 1.27.x |
Copy link
Member Author

Choose a reason for hiding this comment

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

I've removed these as they align with a now-unsupported version of Consul

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport/1.20 Changes are backported to 1.20 pr/no-changelog PR does not need a corresponding .changelog entry type/docs Documentation needs to be created/updated/clarified
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants