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

Consul reporting valid Envoy versions as "not supported" #16493

Closed
nathancoleman opened this issue Mar 1, 2023 · 1 comment · Fixed by #16491
Closed

Consul reporting valid Envoy versions as "not supported" #16493

nathancoleman opened this issue Mar 1, 2023 · 1 comment · Fixed by #16491

Comments

@nathancoleman
Copy link
Member

nathancoleman commented Mar 1, 2023

Overview of the Issue

Consul 1.15.0 is reporting newer releases of Envoy - 1.25.1, for example - as not supported, even though these versions are listed as valid in the compatibility matrix.


Reproduction Steps

  1. Set up Consul 1.15.0 with the latest version of Envoy, 1.25.1
  2. Observe warning when attempting a command such as
    $ consul connect envoy -mesh-gateway -register -service dc1-mgw -partition=default -address x.x.x.x ...
    ...
    Envoy version 1.25.1 is not supported. If there is a reason you need to use this version of envoy use the ignore-envoy-compatibility flag. Using an unsupported version of Envoy is not recommended and your experience may vary. For more information on compatibility see https://developer.hashicorp.com/consul/docs/connect/proxies/envoy#envoy-and-consul-client-agent

Consul info for both Client and Server

Client info
Output from client 'consul info' command here
Client agent HCL config
Server info
Output from server 'consul info' command here
Server agent HCL config

Operating system and Environment details

Log Fragments

@nathancoleman nathancoleman linked a pull request Mar 1, 2023 that will close this issue
3 tasks
@nathancoleman
Copy link
Member Author

This issue is resolved by #16491 which has merged and will be included in Consul 1.15.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant