kubernetes: make the terminating-pod policy configurable in pods mode
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 53/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- elixir, kubernetes
调研方向
Start by reading the Kubernetes strategy code for pods mode and the change associated with issue #114, which introduced the current terminating-pod behavior. Trace how pod deletion timestamps and running state affect discovery, then check the strategy tests and configuration documentation. Done means an opt-in :include setting keeps running terminating pods visible while the default :exclude behavior remains unchanged.
由索引模型根据 Issue 内容生成。
描述
Steps to reproduce
- Configuration Used:
Cluster.Strategy.Kuberneteswithkubernetes_ip_lookup_mode: :pods. - Strategy Used:
Cluster.Strategy.Kubernetes(pods mode). - Errors/Incorrect Behaviour Encountered: the terminating-pod policy is fixed. 3.6.0 excludes pods with a
metadata.deletionTimestamp, which is the right default for deployments that want an unreachable target removed quickly.
Description of issue
This is an improvement request, not a bug: make the terminating-pod policy configurable in pods mode, keeping 3.6.0 as the default. 3.6.0 introduced the current behavior to address #114, but it also removed the ability to express the opposite case.
The use case is a distributed application where a node has to stay reachable while it shuts down. Process groups are one example: if a node leaves discovery as soon as its pod is marked for deletion, it can disappear from :pg before it has finished draining, and peers may start replacement processes while the old ones are still unwinding. Other examples are a node handing off a lease, or a supervised job it owns, before it goes away.
Today there is no way to keep that node visible: pods mode removes it, and endpoints and EndpointSlice modes drop terminating endpoints too. A field selector can't express it either, because a terminating pod keeps phase: Running and metadata.deletionTimestamp is not a selectable field.
Would an opt-in option be acceptable?
kubernetes_pod_terminating: :exclude | :include
:exclude(default): current behavior, remove a pod as soon as it has adeletionTimestamp.:include: keep it until it is no longerRunning, which is what a draining node needs.
The documentation is correct for the default; this would add an option instead of changing behavior.
- 主要语言
- Elixir
- 星标
- 2.2k
- 派生
- 202
- 平均合并
- 2 分钟
- 30 天内合并 PR
- 1
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
bitwalker/libcluster 的其他 Issue
-
难度 4/5 3-5 天 新手友好度 48/100
bitwalker/libcluster#223 ·
-
feature
难度 3/5 1-2 天 新手友好度 38/100
bitwalker/libcluster#191 · 1 条评论 ·
-
难度 5/5 一周以上 新手友好度 25/100
bitwalker/libcluster#139 · 3 条评论 · 8 个 reaction ·
查看 bitwalker/libcluster 的全部 Issue
相似的 Issue
-
Heavy legs 1.12–1.17: compiler corpus goldens not regenerated for #4770可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭
难度 2/5 1-3 小时 新手友好度 74/100
intellij-elixir/intellij-elixir#4782 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 62/100
hexlet-codebattle/codebattle#2376 ·
-
level 2 wocs
难度 1/5 1 小时以内 新手友好度 90/100
phravins/QuantumBilling#51 ·
-
fix(ocr): compile the Tesseract-free pipeline with Tokio runtime可能已有人在做 @Goldziher 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 70/100
carverauto/serviceradar#6898 ·
维护者通常 1 天内回复