大网数据广告活动
服务器运维问答

Routing to ClusterIP via VPN

· 52CE 我爱测

I have the following IP range as ClusterIP from Kubernetes cluster. $ gcloud beta container clusters describe CLUSTER_NAME | grep servicesIpv4Cidr servicesIpv4Cidr: 10.86.240.0/20 I want to allow this IP range accessible from my …

问题原文

原帖链接 · Mr.Wang from Next Door · CC BY-SA 3.0

I have the following IP range as ClusterIP from Kubernetes cluster.

$ gcloud beta container clusters describe CLUSTER_NAME | grep servicesIpv4Cidr
servicesIpv4Cidr: 10.86.240.0/20

I want to allow this IP range accessible from my DC via VPN. After adding the "Remote peer IP address" to the next hop from my DC

How should I create the route on GCE?

According to the doc of gcloud compute routes create command

Exactly one of --next-hop-address, --next-hop-gateway, --next-hop-vpn-tunnel, or --next-hop-instance must be provided with this command.

If I set one of the NODE to --next-hop-instance, what if this NODE is down? How can I implement a route without single-point-of-failure?

已采纳解答

原帖链接 · Carlos · CC BY-SA 3.0

As mentioned here there is not elegant solution at this point. I believe Kubernetes itself will take care of the nodes health in case of failure. Nevertheless, you can still add multiple routes to different nodes. The lowest route will take preference, but if the node ceases to exist the second route will take over.

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2016-04-05)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 3.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。