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

docs: clarify Envoy and dataplane LTS support policy #21337

Merged
merged 1 commit into from
Oct 17, 2024

Conversation

zalimeni
Copy link
Member

Update matrices and clarify statements as to when Consul expands support to new major versions of Envoy and Consul dataplane in light of Consul LTS or Envoy EOL status.

PR Checklist

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

@zalimeni zalimeni added type/docs Documentation needs to be created/updated/clarified pr/no-changelog PR does not need a corresponding .changelog entry backport/1.19 This release series is longer active on CE, use backport/ent/1.19 backport/1.18 This release series is longer active on CE, use backport/ent/1.18 labels Jun 13, 2024
@zalimeni zalimeni requested a review from a team as a code owner June 13, 2024 21:12
@zalimeni zalimeni force-pushed the zalimeni/update-envoy-version-docs branch from 65c0297 to 278b583 Compare June 13, 2024 21:13
@zalimeni zalimeni changed the title docs: clarify Envoy LTS support policy docs: clarify Envoy and dataplane LTS support policy Jun 13, 2024
Update matrices and clarify statements as to when Consul expands
support to new major versions of Envoy and Consul dataplane in light of
Consul LTS or Envoy EOL status.
@zalimeni
Copy link
Member Author

@blake @jkirschner-hashicorp bumping this for your review so it doesn't get lost in the stale PR pile. Not urgent but would love to get it merged if we can soon. Thanks!

@zalimeni zalimeni added backport/1.20 Changes are backported to 1.20 and removed backport/1.19 This release series is longer active on CE, use backport/ent/1.19 backport/1.18 This release series is longer active on CE, use backport/ent/1.18 labels Oct 17, 2024
@zalimeni
Copy link
Member Author

Manually backporting to 1.19 and 1.18 LTS docs in CE after merge.

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