-
Notifications
You must be signed in to change notification settings - Fork 15.1k
[zh-cn]sync gateway #53378
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
base: main
Are you sure you want to change the base?
[zh-cn]sync gateway #53378
Conversation
Signed-off-by: xin.li <[email protected]>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
✅ Pull request preview available for checkingBuilt without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify project configuration. |
| underlying Gateway implementation. For example, defining a new GRPCRoute may result in configuring additional | ||
| traffic routes in a cloud load balancer or in-cluster proxy server. | ||
| --> | ||
| GRPCRoute 类型指定了从 Gateway 监听器到后端网络端点的 gRPC 请求路由行为。 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| GRPCRoute 类型指定了从 Gateway 监听器到后端网络端点的 gRPC 请求路由行为。 | |
| GRPCRoute 类别指定从 Gateway 监听器到后端网络端点的 gRPC 请求路由行为。 |
| traffic routes in a cloud load balancer or in-cluster proxy server. | ||
| --> | ||
| GRPCRoute 类型指定了从 Gateway 监听器到后端网络端点的 gRPC 请求路由行为。 | ||
| 对于服务后端,实现可以将后端网络端点表示为服务 IP 或服务的后端 EndpointSlices。 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| 对于服务后端,实现可以将后端网络端点表示为服务 IP 或服务的后端 EndpointSlices。 | |
| 对于服务后端,实现可以将后端网络端点表示为服务 IP 或服务的若干后端 EndpointSlice。 |
| See the [GRPCRoute](https://gateway-api.sigs.k8s.io/reference/spec/#grpcroute) | ||
| reference for a full definition of this API kind. | ||
| --> | ||
| 在这种情况下,GRPCRoute 将匹配任何发往 svc.example.com 的流量,并应用其路由规则 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| 在这种情况下,GRPCRoute 将匹配任何发往 svc.example.com 的流量,并应用其路由规则 | |
| 在这种情况下,GRPCRoute 将匹配任何发往 `svc.example.com` 的流量,并应用其路由规则 |
| reference for a full definition of this API kind. | ||
| --> | ||
| 在这种情况下,GRPCRoute 将匹配任何发往 svc.example.com 的流量,并应用其路由规则 | ||
| 将流量转发到正确的后端。由于仅指定了一个匹配项,因此只有发往 svc.example.com 的 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| 将流量转发到正确的后端。由于仅指定了一个匹配项,因此只有发往 svc.example.com 的 | |
| 将流量转发到正确的后端。由于仅指定了一个匹配项,因此只有发往 `svc.example.com` 的 |
| --> | ||
| 在这种情况下,GRPCRoute 将匹配任何发往 svc.example.com 的流量,并应用其路由规则 | ||
| 将流量转发到正确的后端。由于仅指定了一个匹配项,因此只有发往 svc.example.com 的 | ||
| com.example.User.Login 方法请求会被转发。 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| com.example.User.Login 方法请求会被转发。 | |
| `com.example.User.Login` 方法请求会被转发。 |
| 在这种情况下,GRPCRoute 将匹配任何发往 svc.example.com 的流量,并应用其路由规则 | ||
| 将流量转发到正确的后端。由于仅指定了一个匹配项,因此只有发往 svc.example.com 的 | ||
| com.example.User.Login 方法请求会被转发。 | ||
| 任何其他方法的 RPC 不会由这个 Route 匹配。 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| 任何其他方法的 RPC 不会由这个 Route 匹配。 | |
| 所有其他 RPC 方法都不会被这个 Route 匹配。 |
content/zh-cn/docs/concepts/services-networking/gateway.md