2019-11-01 11:22:49 +08:00
<!--
#
# Licensed to the Apache Software Foundation (ASF) under one or more
# contributor license agreements. See the NOTICE file distributed with
# this work for additional information regarding copyright ownership.
# The ASF licenses this file to You under the Apache License, Version 2.0
# (the "License"); you may not use this file except in compliance with
# the License. You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
#
-->
2020-06-19 12:03:55 +08:00
[中文 ](zh-cn/grpc-proxy.md )
2020-04-20 09:07:42 +08:00
2019-11-01 10:09:01 +08:00
# grpc-proxy
proxying gRPC traffic:
2021-01-26 11:04:16 +08:00
gRPC client -> APISIX -> gRPC/gRPCS server
2019-11-01 10:09:01 +08:00
2020-04-20 09:07:42 +08:00
## Parameters
2019-11-01 10:09:01 +08:00
2021-01-26 11:04:16 +08:00
* `scheme` : the `scheme` of the route's upstream must be `grpc` or `grpcs` .
* `uri` : format likes /service/method, Example: /helloworld.Greeter/SayHello
2019-11-01 10:09:01 +08:00
### Example
2019-11-01 11:22:49 +08:00
#### create proxying gRPC route
2019-11-01 10:09:01 +08:00
Here's an example, to proxying gRPC service by specified route:
2021-01-26 11:04:16 +08:00
* attention: the `scheme` of the route's upstream must be `grpc` or `grpcs` .
2019-11-14 11:57:16 +08:00
* attention: APISIX use TLS‑ encrypted HTTP/2 to expose gRPC service, so need to [config SSL certificate ](https.md )
* the grpc server example: [grpc_server_example](https://github.com/iresty/grpc_server_example)
2019-11-01 10:09:01 +08:00
```shell
2020-11-28 19:05:14 +08:00
curl http://127.0.0.1:9080/apisix/admin/routes/1 -H 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -X PUT -d '
2019-11-01 10:09:01 +08:00
{
"methods": ["POST", "GET"],
"uri": "/helloworld.Greeter/SayHello",
"upstream": {
2021-01-26 11:04:16 +08:00
"scheme": "grpc",
2019-11-01 10:09:01 +08:00
"type": "roundrobin",
"nodes": {
"127.0.0.1:50051": 1
}
}
}'
```
#### testing
Invoking the route created before:
```shell
$ grpcurl -insecure -import-path /pathtoprotos -proto helloworld.proto -d '{"name":"apisix"}' 127.0.0.1:9443 helloworld.Greeter.SayHello
{
"message": "Hello apisix"
}
```
This means that the proxying is working.
2021-01-26 11:04:16 +08:00
### gRPCS
If your gRPC service encrypts with TLS by itself (so called `gPRCS` , gPRC + TLS), you need to change the `scheme` to `grpcs` . The example above runs gRPCS service on port 50052, to proxy gRPC request, we need to use the configuration below:
```shell
curl http://127.0.0.1:9080/apisix/admin/routes/1 -H 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -X PUT -d '
{
"methods": ["POST", "GET"],
"uri": "/helloworld.Greeter/SayHello",
"upstream": {
"scheme": "grpcs",
"type": "roundrobin",
"nodes": {
"127.0.0.1:50052": 1
}
}
}'
```