-
Notifications
You must be signed in to change notification settings - Fork 7.6k
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
Istio transforming grpc requests in a way not supported by client? #49685
Comments
If you can get full debug logs from the client it would be ideal. |
I can't transfer the logs, but I can retype particular lines, sorry. What I see is:
|
I have the same problem. Related LogsUsing
|
This issue may be fixed in the envoy release v1.29.3. Related |
I was able to temporarily work around this problem by setting defaultConfig:
runtimeValues:
envoy.reloadable_features.sanitize_te: "false" or annotations:
proxy.istio.io/config: |
runtimeValues:
envoy.reloadable_features.sanitize_te: "false" |
0.2.8 (3-27-24) --- - revert back to `1.20.4-solo` Istio images and `1-20` revision tag due to [#49685](istio/istio#49685)
0.2.8 (3-27-24) --- - revert back to `1.20.4-solo` Istio images and `1-20` revision tag due to [#49685](istio/istio#49685)
We ran into this issue too - solved it by downgrading to v1.20.0 |
This workaround worked for me too, thanks for sharing @frauniki |
This issue has been fundamentally resolved with the release of istio/proxy v1.21.1. |
Agree that 1.21.1 solves the issue. Thanks! |
Is this the right place to submit this?
Bug Description
We are using a gRPC service that when the port name on the service is gRPC, the service gives an error saying:
UNKNOWN:Error received from peer {grpc_message:"Missing :te header", grpc_status:2, created_time:"<current time>"}
, but if we change the port name to tcp it works.Version
Additional Information
I cannot include the output of that command because the cluster is air-gapped. Key logs are:
Calling client error:
UNKNOWN:Error received from peer {grpc_message:"Missing :te header", grpc_status:2, created_time:"<current time>"}
Calling istio-proxy log:
[<Timestamp>] "POST /endpoint HTTP/2" 200 - via_upstream - "-" 5 0 112 111 "-" "grpc-python/1.60.0 grpc-c/37.0.0 (linux; chttp2)" "<uuid>" "<destination service> <destination pod ip>:3030" outbound|3030||<fqdn of destination service> <caller ip>:48238 <destination service ip> - default
Destination pod application log: everything normal
attempted with Istio-proxy both enabled and disabled on the destination, getting the same error. If istio-proxy is enabled, it shows a 200 as well, same as the calling istio proxy
The text was updated successfully, but these errors were encountered: