-
Notifications
You must be signed in to change notification settings - Fork 407
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
Some HTTP/2 requests fail with duplicate value in envoy authority request header #18631
Comments
Update on this:
CC @barchw as FYI because they were on the last Kyma ticket I wrote up on this subject. ℹ️ Istio module |
I will add it to our backlog. |
ℹ️ The fix for this issue is now included in the Istio 1.20.5 release. If you produce v1.4.3 of the Istio module and bump the release to 1.20.5, the issue will likely be resolved. But I won't pretend to know what other considerations have to go into something like that at your scale! :) Looking forward to seeing these changes roll into Kyma soon either in the next 1.5 or 1.4.x module. Thanks for your willingness to engage with this in public! |
Nevermind, I see the 1.5x module is already available. I'll have to wait until it rolls out to us on BTP Kyma and then check. 👍 |
Hey @SeanKilleen, Istio module 1.5 (with Istio 1.21.1) rolled out to Regular channel last week, you should have it already on your cluster. |
A continuation of #18447, which was previously closed.
After removing our prior workaround recently, I noted that the issue persisted.
There was some confusion between myself and the Istio team -- changes that I thought were back-ported to Envoy 1.28.x and 1.27.x were not. The Istio member was asking me to work to get the changes back-ported, but their wording gave me the impression that the changes had been back-ported.
As such, the issue persists and a fix is not yet available for Kyma. Therefore, opening this to track the state of that fix as I work through it with the Istio team.
The text was updated successfully, but these errors were encountered: