Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Corner Case: Clenup Processing for Delete Event Without Finalizer

未关闭
#1,597 3 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
停滞
技术栈
java, kubernetes

调研方向

从 @ControllerConfiguration 注解开始,追踪 Cleaner 实现如何在删除 custom resource 期间触发 finalizer 处理。确认 delete event 在哪里处理,以及如何调用 cleanup。完成的标准是:所提出的配置能够控制 cleaner 是否添加 finalizer,而不改变 cleanup 行为,并且相关行为有测试覆盖。

由索引模型根据 Issue 内容生成。

描述

feature

If Cleaner interface is implemented by a reconciler a finalizer is automatically added to the custom resource, and cleaner is called before it gets removed.
There is however a corner case when it makes sense to do cleanup event finalizer is not used. In case there is an in memory data held for a custom resource, so when a custom resource deleted, related indexed or in memory objects needs to be cleaned up. In this case a finalizer is not needed, since if the operator is down and the delete event is missed it's not a problem, since the cleanup is just for in memory data.

To support this we could add a feature flag to @ControllerConfiguration to don't add finalizer for cleanup: addFinalizerForCleaner.

Note that this is not a priority issue, we should probably implement it only if some requests it. Also having a finalizer in those cases would not be a big issues.

主要语言
Java
星标
944
派生
242
平均合并
1 天 14 小时
30 天内合并 PR
46

贡献指南

打开贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

operator-framework/java-operator-sdk 的其他 Issue

查看 operator-framework/java-operator-sdk 的全部 Issue

相似的 Issue

更多 Java Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。