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

What's necessary for a bare metal dual stack kubernetes setup?

· 52CE 我爱测

We are about to start setting up a new kubernetes cluster on bare metal at our own datacenter. The documentation for the k8s moduls and services is great, however I was not able to find any comprehensive top view documentation on…

问题原文

原帖链接 · Daniel Becker · CC BY-SA 4.0

We are about to start setting up a new kubernetes cluster on bare metal at our own datacenter. The documentation for the k8s moduls and services is great, however I was not able to find any comprehensive top view documentation on the components necessary to meet our requirements:

Pods need to be reachable via IPv4 and IPv6 Pods need to be able to move between hosts and still be reachable on both protocols Pods need to reach outside resources through IPv4 and IPv6 I know that one can use MetalLb for ingress traffic management. But would that also work when a pod tries to reach an external v4/v6 resource?

What would be necessary, overall, to satisfy the requirements?

已采纳解答

原帖链接 · Sander Steffann · CC BY-SA 4.0

I used Kubernetes 1.21 with Calico for networking behind my BGP router/firewall (Juniper SRX) for external connectivity. Calico can be combined with metallb where metallb does the orchestration and Calico does the BGP routing. See https://docs.projectcalico.org/networking/advertise-service-ips#advertise-service-load-balancer-ip-addresses for more details on that.

Add nginx for ingress and cert-manager for certificates, and you should have everything you need.

I did notice that the load balancer doesn't handle dual stack, but you can easily work around that by creating two separate ones: one single stack IPv6 and one single stack IPv4.

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

资料来源与适用范围

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

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

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