Use External Subnets for Service Controller
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 38/100
- Issue 类型
- 功能
- 描述清晰度
- 需要澄清
- 活跃度
- 冷清
- 技术栈
- go, kubernetes
- 领域
- backend, cloud, networking
调研方向
从 internal/provider/load_balancer.go 开始，重点查看当前的 Floating IP 实现，以及链接行附近的负载均衡器状态处理。阅读外部子网文档，并调查子网池、/32 分配、注解和节点监听将如何工作。建立并实现一个可行的外部子网设计，以移除当前的 IP:PORT 冲突限制，即视为完成。
由索引模型根据 Issue 内容生成。
描述
The service controller currently uses floating IPs as the implementation for LoadBalancer services. This presents the following issues.
- Floating IPs are transparent to the instance—traffic arrives on the instance's internal IP address instead of the floating IP address. To work around this we add the instance's internal IP address to the load balancer status, which is technically incorrect.
- Due to the above point, we cannot create two different load balancers using the same service port on the same Kubernetes node. Otherwise, there will be a port conflict.
Let's explore using external subnets instead of floating IPs as the implementation for LoadBalancer services. This would solve the limitations with floating IPs, and create some new limitations, described below.
- The subnet pool that the external subnet is allocated from must already exist and be provided to the
LoadBalancerservice. This could presumably be done using annotations (e.g.,oxide.computer/subnet-pool). - Attaching an external subnet to an instance does not automatically make the instance listen on any of the IP addresses in that subnet. That is, there would need to be some mechanism to tell the Kubernetes node to listen on an IP address from the attached external subnet. I'm thinking the implementation would allocate
/32IP addresses from the external subnet and use that as the external address in theLoadBalancerstatus. That should configure the Kubernetes node to listen on that IP address but perhaps I'm mistaken and further discovery is needed here.
Assuming further discovery proves fruitful, switching to external subnets for LoadBalancer services could significantly improve the current state of Kubernetes on Oxide by lifting the IP:PORT conflict limitation that floating IPs currently have.
- 主要语言
- Go
- 星标
- 6
- 派生
- 2
- 平均合并
- 2 小时 50 分钟
- 30 天内合并 PR
- 7
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
oxidecomputer/oxide-cloud-controller-manager 的其他 Issue
-
Documentation Kubernetes Cloud Controller Manager (CCM)
难度 2/5 1-3 小时 新手友好度 74/100
-
Documentation Kubernetes Cloud Controller Manager (CCM)
难度 2/5 1-3 小时 新手友好度 90/100
-
Bug Kubernetes Cloud Controller Manager (CCM)
难度 2/5 1-3 小时 新手友好度 78/100
-
Bug Kubernetes Cloud Controller Manager (CCM)
难度 2/5 1-3 小时 新手友好度 78/100
oxidecomputer/oxide-cloud-controller-manager#275 · 1 条评论 ·
-
Enhancement Kubernetes Cloud Controller Manager (CCM)
难度 2/5 1-3 小时 新手友好度 86/100
查看 oxidecomputer/oxide-cloud-controller-manager 的全部 Issue
相似的 Issue
-
bug
难度 2/5 1-3 小时 新手友好度 72/100
Billionmail/BillionMail#389 ·
-
good first issue help wanted v3
难度 2/5 1-3 小时 新手友好度 77/100
oras-project/oras-go#1621 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 80/100
维护者通常 4 天内回复
-
难度 2/5 1-3 小时 新手友好度 67/100
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
kaimahi-agents/kaimahi#570 ·
维护者通常 1 天内回复