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

bug: PublishedResource updates leave previous sync controllers active

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

@adoi 已经在做这个了。

开始于 2026年7月20日。

评估

这个 Issue 还没有评估数据。

描述

kind/bug
Describe the bug

When updating a PublishedResource the manager starts a replacement without stopping the controller for the previous resource version. Both controllers then reconcile the same resources

Steps To Reproduce
  1. Run api syncagent with an active PR
  2. Update the PR (in my case spec.naming was changed, but it can be an annotation change)
  3. Check a new controller will start for the new resource, but the previous controller doesn't stop
  4. You can also create a synchronized resource again and you will see that both (or multiple) controllers will process it
Expected Behaviour

One sync controller should be active per PR. A replacement should be validated, then the existing controller drained before the replacement starts

Additional Context

I reproduced this with v0.7.0.

During my testing and implementation I checked that immediate replacement can overlap controllers. Stopping before validation can interrupt synchronization, so my approach for the solution is object key tracking with validate, drain, then start sequencing

主要语言
Go
星标
25
派生
30
平均合并
5 天 18 小时
30 天内合并 PR
1

环境准备

从这里开始

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

kcp-dev/api-syncagent 的其他 Issue

查看 kcp-dev/api-syncagent 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

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