Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

bug: PublishedResource updates leave previous sync controllers active

Open
#182 1 comment 0 reactions 1 assignee View on GitHub

@adoi is already working on this.

Since Jul 20, 2026.

Assessment

This issue has not been assessed yet.

Description

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

Dominant language
Go
Stars
25
Forks
30
Avg merge
3d 9h
Merged PRs (30d)
2

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from kcp-dev/api-syncagent

All issues in kcp-dev/api-syncagent

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.