-
Notifications
You must be signed in to change notification settings - Fork 324
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
Add consul v1.11.3 support in consul k8s and helm chart #1035
Comments
Hi @FelipeEmerim you could easily upgrade to 1.11.3 using your existing Helm chart as described here: https://www.consul.io/docs/k8s/upgrade#consul-version-upgrade. It is best practice to set the |
Thank you for the quick response, I will try bumping the image as you said. |
It worked, than you! |
Great, I'll close this issue but we'll make sure to roll out 1.11.3 as the default shortly. Thanks! |
Hi just an update, we'll actually be rolling out to 1.11.4 instead as the default sometime next week instead of 1.11.3 since there is a UI bug on Consul that folks are hitting. |
Thank you for the notice. We will keep an eye out for the new update. |
Community Note
Is your feature request related to a problem? Please describe.
Consul 1.11.3 introduces several fixes. This one is very critical and is causing downtime on our ingress controller.
Feature Description
I would like consul k8s and its helm chart to support consul v1.11.3.
Use Case(s)
To get consul's latest bugfixes, including the one mentioned above that solves a problem with ingress controllers which use the dialedDirectly feature of transparent proxy.
Contributions
We could open a PR following #976, but I do not think that is possible since community PRs cannot add Changelog entries.
The text was updated successfully, but these errors were encountered: