Google Cloud API网关和云在私有上下文中运行
我在云运行后端的前面有一个Google Cloud API网关。如果两者都是公共的，一切都可以。
如果我检查在云运行时仅允许内部流量，则API网关无法访问后端。有没有办法在API网关和云运行之间保持私人连接？
另一个问题。有没有一种方法可以使用私有IP在网络中使用API网关？
I have a Google Cloud Api Gateway in front of a Cloud Run Backend. If both are public everything works.
If I check Allow internal traffic only on Cloud Run, Api Gateway does not have access to the backend. Is there a way to keep a private connection between Api Gateway and Cloud Run?
Another question. Is there a way to have an Api Gateway inside my network using a private IP?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
当Guillaume Blaquiere提到现在是不可能的。
当将API网关与云运行一起使用时，不可能仅允许从云运行中进行内部流量，以便仅允许云运行的VPC网络中的流量，这是此设置的唯一可用选项。
云运行服务设置为内部的入学流量无法接受API网关的请求，API网关在路线图上没有任何将流量标记为“内部”到无服务器后端的任何内容。
由于有功能请求支持更新Ingress设置以包括在内来自API网关的内部流量和Intress Internal，您将拥有一个“私人” IP供您服务。
Answering this as community wiki.As guillaume blaquiere mentioned it is not possible for now.
When using API Gateway with Cloud Run, it should not be possible to allow only internal traffic from Cloud Run in order to only allow traffic from within Cloud Run’s VPC Network,all ingress which is the only option available for this setup.
Cloud Run service with ingress traffic set to Internal could not accept requests from API Gateway, API Gateway does not have anything on the roadmap for marking traffic as "internal" to serverless backends.
This may be available in future since there is a Feature Request to support updating the ingress settings to include the option of internal traffic from API Gateway and with the ingress Internal you will have a "private" IP for your service.