You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We will have to note these changes in the Upgrade specific guide as existing Connect-enabled jobs will need restarting to take advantage of the Envoy version bump. Forgetting that step could cause users to prematurely upgrade their Consul clusters to a version of Consul incompatible with running Envoys.
The text was updated successfully, but these errors were encountered:
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Investigate what Envoy version to upgrade to in Nomad v0.12:
https://www.consul.io/docs/connect/proxies/envoy.html#supported-versions
We will have to note these changes in the Upgrade specific guide as existing Connect-enabled jobs will need restarting to take advantage of the Envoy version bump. Forgetting that step could cause users to prematurely upgrade their Consul clusters to a version of Consul incompatible with running Envoys.
The text was updated successfully, but these errors were encountered: