Consul reporting valid Envoy versions as "not supported"
- Dominant language
- Go
- Stars
- 30.1k
- Forks
- 4.6k
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 39
Description
#### Overview of the Issue
Consul compatibility matrix at https://developer.hashicorp.com/consul/docs/reference/proxy/envoy#standard-releases
report that consul 1.19.x (CE) is compatible with envoy versions `1.33.x, 1.32.x, 1.29.x, 1.28.x, 1.27.x, 1.26.x`
---
#### Reproduction Steps
1. Run consul `1.19.2` with an envoy `1.33.14`
2. The `consul connect envoy` command fails with this message in the logs
```
Envoy version 1.33.x 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
```
### 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
Contributor guide
Research direction
Start with the consul connect envoy command's Envoy compatibility check and compare it with the documented Consul 1.19.x compatibility matrix. Reproduce the failure with Consul 1.19.2 and Envoy 1.33.14, then verify the listed valid Envoy versions are accepted without the ignore-envoy-compatibility flag.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100