read-cache-after-write consistency and event filtering for deletes
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 20/100
- Issue 类型
- 功能
- 描述清晰度
- 需要澄清
- 活跃度
- 停滞
- 技术栈
- java, kubernetes
调研方向
首先定位 Java Operator SDK 中用于删除操作的读缓存和事件过滤路径，然后查看父 issue 以了解预期行为。比较有 finalizers 和没有 finalizers 的资源，以及关于乐观锁的注释；只有在删除事件过滤策略确定并得到一致实现后，该 issue 才算完成。
由索引模型根据 Issue 内容生成。
描述
See also parent issue.
This might be a bit problematic, for resource without finalizer:
If the resource does not implement a finalizer, we could just record the UID of the resource and filter out events until we receive the delete event, that removes the cached resource ID.
The issue is with the resources with a finalizer, there we could define this like:
-
Filter just the event that was caused by the delete operation (in this case, it just adds the deletion timestamp), and process subsequent events. By definition, only operations should happen afterwards, and that includes finalizer removals, but that is not enforced on the API level. Note that implementation-wise, this is an issue since the delete operation does not return the new resource nor it's version.
-
We could filter out all the subsequent events until we receive a delete event. - But this might be too opionated, and especially if the controller would be restarted, users might see the resources again (although still marked for deletion). So probably not the right thing to do.
Notes:
- optimistic locking does not seems to work for deletes either
- 主要语言
- Java
- 星标
- 944
- 派生
- 242
- 平均合并
- 1 天 14 小时
- 30 天内合并 PR
- 46
贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
operator-framework/java-operator-sdk 的其他 Issue
-
难度 4/5 3-5 天 新手友好度 55/100
operator-framework/java-operator-sdk#3621 · 8 条评论 · 已指派 1 人 ·
-
难度 4/5 3-5 天 新手友好度 38/100
operator-framework/java-operator-sdk#3615 · 1 条评论 · 3 个 reaction ·
-
难度 4/5 3-5 天 新手友好度 45/100
operator-framework/java-operator-sdk#3568 · 1 条评论 · 1 个 reaction ·
-
难度 5/5 一周以上 新手友好度 25/100
-
operator-framework/java-operator-sdk#3538 · 2 条评论 · 已指派 2 人 ·
查看 operator-framework/java-operator-sdk 的全部 Issue
相似的 Issue
-
area-deployment area-integrations triage:bot-seen
难度 2/5 半天 新手友好度 86/100
-
难度 2/5 1-3 小时 新手友好度 75/100
apache/flink-agents#1156 ·
-
area/connectors autoteam community connectors/source/shopify needs-triage team/use type/bug
难度 2/5 1-3 小时 新手友好度 84/100
-
难度 2/5 1-3 小时 新手友好度 70/100
-
难度 1/5 1 小时以内 新手友好度 85/100