RouteController无法在GKE上创建路由 [英] RouteController failed to create a route on GKE

问题描述

我在GKE上有一个集群，当我想使用该集群时创建其节点池，并在使用完该集群后将其删除.

I have a cluster on GKE whose node pool I create when I want to use the cluster, and delete when I'm done with it.

这是一个两个节点的群集，其中主服务器位于europe-west2-a中，其节点区域为europe-west2-a和europe-west2-b.

It's a two node cluster with the master in europe-west2-a and with and whose node zones are europe-west2-a and europe-west2-b.

最近的创建导致区域B中的节点因NetworkUnavailable而失败，因为RouteController failed to create a route.原因是因为Could not create route xxx 10.244.1.0/24 for node xxx after 342.263706ms: instance not found.

The most recent creation resulted in the node in zone B failing with NetworkUnavailable because RouteController failed to create a route. The reason was because Could not create route xxx 10.244.1.0/24 for node xxx after 342.263706ms: instance not found.

为什么会突然发生这种情况，我该怎么解决?！

Why would this be happening all of a sudden, and what can I do to fix it?!

推荐答案

您没有提到您使用的是哪个版本的GKE，只是为了澄清一下:

You didn't mention which version of GKE you are using so just for clarification:

访问范围中的更改 从Kubernetes版本1.10开始，默认情况下，gcloud和GCP控制台不再授予新集群和新节点池上的compute-rw访问范围.此外，如果在gcloud容器创建中指定了--scopes，则gcloud将不再默默地添加compute-rw或storage-ro.

Changes in access scopes Beginning with Kubernetes version 1.10, gcloud and GCP Console no longer grants the compute-rw access scope on new clusters and new node pools by default. Furthermore, if --scopes is specified in gcloud container create, gcloud no longer silently adds compute-rw or storage-ro.

无论如何，您仍然可以还原到旧版访问范围，但不建议这样做.

In any case you can still revert to legacy access scopes but this is not recommended approach.

希望获得帮助.

这篇关于RouteController无法在GKE上创建路由的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！