olddriver4 opened a new issue, #11206:
URL: https://github.com/apache/apisix/issues/11206
### Current State
```
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: base-grpc
namespace: app
annotations:
kubernetes.io/ingress.class: apisix
k8s.apisix.apache.org/upstream-scheme: grpc
spec:
rules:
- host: "base-grpc.app.ntrnl"
http:
paths:
- path: /*
pathType: Prefix
backend:
service:
name: base
port:
name: grpc
```
`grpcurl -plaintext base-grpc.app.ntrnl:80 list social.base.PortalService`
The protocol configured for k8s apisix ingress grpc does not take effect,
please help me. The error is reported as follows:
Failed to list methods for service "social.base.PortalService": rpc error:
code = Unavailable desc = upstream connect error or disconnect/reset before
headers. reset reason: protocol error
My domain name has been host-resolved, and LB uses Layer 4 TCP protocol. I
would like to know where this problem lies. I have searched for online
configurations but can't solve it!
There is absolutely no problem with the service, because I use svc host to
access it correctly!
This is the configuration of the apisix service：
```
apiVersion: v1
kind: Service
metadata:
name: apisix-gateway
namespace: apisix
labels:
app: apisix
version: "3.7.0"
spec:
type: LoadBalancer
ports:
- name: apisix-gateway-http
port: 80
targetPort: 9080
protocol: TCP
- name: apisix-gateway-https
port: 443
targetPort: 9080
protocol: TCP
selector:
app: apisix
version: "3.7.0"
```
The above are all the steps of my configuration. I really don’t have more
detailed configuration problems. Could you please help me detect whether it is
a configuration problem there or a LB problem? @spa
### Desired State
done
--
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]
