feature: Mirror service cluster events into kcp

Open
#88 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start by reading issue #17 and the existing agent event-creation path. Determine how service-cluster events, synced objects, origin objects, permissions, and any PublishedResource configuration are represented. Done means the scope and design for filtering, mapping, and mirroring relevant events into kcp are agreed and implemented with validation.

Written by the indexing model from the issue text.

Description

kind/feature
Feature Description

This is an extension to #17. The agent can already create events that relate to its own operation.

What would be nice is if the agent was able to mirror all events that happen on the service cluster and relate to objects it has synced down, up into kcp.

Proposed Solution

For this the agent would roughly

  • subscribe to all events in the service cluster
  • filter out events for uninteresting objects
  • figure out what the origin object is (in kcp) for every interesting object on the service cluster
  • copy the event

Since we cannot control the source of events (any random 3rd party operator could create them), the agent might need to have a sort of allowlist for event types that it mirrors (if so, most likely configured in the PublishedResource).

This might all be tricky to achieve, since the agent might need to get the object for every event, and it simply doesn't have permissions to get random objects in the service cluster.

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.