feature: bidirectional synchronization of existing resources on remote clusters

Open
#129 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
go, kubernetes
Domain
backend-api-design, distributed-systems

Research direction

Start by reviewing kcp and kcp syncagent's existing resource synchronization and discovery behavior for remote clusters. Define how resources created outside kcp should be discovered, listed, and retrieved through the centralized API, then identify tests that can verify bidirectional synchronization and reconciliation.

Written by the indexing model from the issue text.

Description

kind/feature
Feature Description

I would like to use kcp and kcp syncagent to create and manage resources on remote clusters through a centralized API.
However, it seems, they do not natively support to discover resources that were created outside of kcp.
I mean, I created resources directly on my remote clusters, I would like to be able to list/get them on kcp.

Proposed Solution

feature to automatically synchronize the state of existing resources created with or without KCP on remote clusters

Alternative Solutions

No response

Want to contribute?
  • I would like to work on this issue.
Additional Context

No response

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.