kubernetes: opt-in to connect only to Ready pods
还没有人认领这个 Issue。
评估
调研方向
Start by reading the Kubernetes strategy implementation and its tests for pods mode; the issue does not name specific files. Trace how discovered pod conditions affect which pods are connected, then check how the proposed opt-in setting fits the existing configuration and documentation. Done means the default preserves current behavior and the ready-only option connects only to pods with a Ready condition of True.
由索引模型根据 Issue 内容生成。
描述
Steps to reproduce
- Configuration Used:
Cluster.Strategy.Kubernetes,kubernetes_ip_lookup_mode: :pods, any namespace/selector. - Strategy Used:
Cluster.Strategy.Kubernetes(pods mode). - Errors/Incorrect Behaviour Encountered: the strategy connects to every discovered pod that is
Running, has an IP and is not terminating, including pods whoseReadycondition isFalse.
Description of issue
That behavior is deliberate (the docs say readiness can depend on cluster formation), but it rules out a common deployment shape: only dialling a peer once it is actually serving. In our case a pod that is distributed but still booting should be discovered yet not connected to, because the work handlers are not up.
Endpoints and EndpointSlice modes gate on readiness, but they're a flat address list that drops terminating endpoints, so they can't express "discovered but not dialable". Pods mode already returns the conditions, so no extra request is needed.
Would an opt-in option in pods mode be acceptable in principle?
kubernetes_pod_readiness: :any | :ready
:any(default) keeps connecting to non-ready Running pods, as today.:readyonly connects to pods whoseReadycondition isTrue.
The documentation is correct as written; this would be an additional mode rather than a correction.
- 主要语言
- 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 天 新手友好度 53/100
bitwalker/libcluster#224 · 1 个 reaction ·
-
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 天内回复