wolgod commented on issue #1230: URL: https://github.com/apache/apisix-ingress-controller/issues/1230#issuecomment-1207913364
> ### Issue description >  > > I see the grpc can use without ssl, as the doc show in the apisix . > > But as the apisix-ingress way, can I config grpc without ssl ? ( the doc : proxy-grpc-service.md ) > > I have try it like this  > > and test it： grpcurl -servername grpc-proxy 172.16.11.61:30981 yages.Echo.Ping Failed to dial target host "172.16.11.61:30981": tls: first record does not look like a TLS handshake > > ### Environment > * your apisix-ingress-controller version (output of apisix-ingress-controller version --long): 1.4 > * your Kubernetes cluster version (output of kubectl version): 1.21 > * if you run apisix-ingress-controller in Bare-metal environment, also show your OS version (uname -a): in k8s If you proxy the port 80 used by http, you must set a separate http port to proxy http2, so as to support clear text transmission, not ssl -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
