Google Cloud Run 404 服务之间的内部流量错误
[英]Google Cloud Run 404 Error on internal traffic between services
问题描述
I am currently trying to connect two Google Cloud Run services.
我目前正在尝试连接两个 Google Cloud Run 服务。 Both use the default service account, are deployed in europe-west1 , require no IAM-authentication and only accept internal traffic (and load balancing traffic).两者都使用默认服务帐户，部署在europe-west1 ，不需要 IAM 身份验证，只接受内部流量（和负载平衡流量）。 I have following architecture我有以下架构
Load Balancer
|
` /service -------> service-0 -------> service-1
service-0 acts as reverse proxy that adds some authentication headers and is connected to service-1 via its https://<service-1>.run.app url. service-0充当反向代理，添加一些身份验证标头，并通过其https://<service-1>.run.app url 连接到service-1 。 Whenever I try to connect to service-1 from the Internet (via Load Balancer and service-0 ) I get a 404 error from the ingress sitting in front of service-1 .每当我尝试从 Internet 连接到service-1时（通过负载均衡器和service-0 ），我都会从service-1前面的入口处收到 404 错误。 I can verify that service-0 forwards the request correctly.我可以验证service-0是否正确转发了请求。
However when I expose service-1 to the internet, I reach the service without any problems.但是，当我将service-1公开到 Internet 时，我可以毫无问题地访问该服务。
This post Google Load Balancer to Cloud Run giving 404 suggests that it is an issue with europe-west1 region, but I cannot simply switch the region.这篇Google Load Balancer to Cloud Run 的帖子给出 404表明这是 europe-west1 区域的问题，但我不能简单地切换区域。 Any help would be appreciated.任何帮助，将不胜感激。
1 个解决方案
解决方案1
0 已采纳 2022-08-15 10:34:03
After some time now, it turned out to be a Problem with Google Cloud Run in europe-west1.一段时间后，事实证明这是欧洲西部 Google Cloud Run 的问题1。 We contacted support and switched to GKE.我们联系了支持人员并切换到 GKE。
声明:本站的技术帖子网页，遵循CC BY-SA 4.0协议，如果您需要转载，请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.