Jiezhang Wang
Jiezhang Wang
1. create your grpc-app-deploment.yaml 2. create your grpc grpc-app-service.yaml, server.yaml may like: ``` kind: Service apiVersion: v1 metadata: name: your-grpc-app-svc spec: selector: app: your-grpc-app ports: - protocol: TCP port: 80...
> I found the gateway don't support https I need some logs.
@abhinavjha126 Change the protocol from GRPC to TCP, like: ``` ... - hosts: - '*.web.com' port: name: grpc-0 number: 9000 protocol: TCP ```
Yes, edgemesh support for pod ip communication is planned. However, the exact plan is still very much up for discussion. **what problem do we need to solve**: - edgemesh supports...
This may be a known kubeedge issue. You can refer to: https://github.com/kubeedge/kubeedge/issues/3489
> Issue 1: Kubectl logs cannot read the pod log for this Error pod. This has nothing to do with edgemesh, you need to enable the stream function of kubeedge....
Impotant Error Info: dail tcp 127.0.0.1:10550 You need to enable your edgecore metaServer config.
> the edgecore metaServer startup is not working. You can submit an issue to kubeedge repo.
need your edgemesh-gateway logs
> it is not able to recognize vs with host "app.mydomain.com" Maybe this error: ``` 2022-03-29T05:52:38.859565574+00:00 stderr F E0329 05:52:38.859539 1 server.go:133] get pb from conn err: no match virtual...