Skip to content

feature: Make shards to own shard object locally  #4335

Closed

Description

@mjudeikis

Feature Description

Now every shard writes its shard object into root shard. Making root shart more special than it should be. In addition data is getting hard to handle. In example if we want to track shard status, every shards now writes this via expensive network call, vs locally.

Proposed Solution

We create new dedicated "hidden" workspace system:shard
We add shard object into this on every shard (one object only per shard). And shard use this to store data, statuses, etc
We replicate this shard object into cache server same lc.
We pull this into root shard as representation only.

Consequence of this is one can't edit shard object spec anymore and just change its configuration. Which is fine. At some point we can establish two way sync from designated representation location (root shard root workspace), but for now if you want to change something - you change shard configuration/deployment and see it replicate.

Alternative Solutions

No response

Want to contribute?

  • I would like to work on this issue.

Additional Context

No response

Activity

  1. added
    kind/featureCategorizes issue or PR as related to a new feature.
    on Aug 21, 2026
  2. self-assigned this
    on Aug 21, 2026
  3. changed the title [-]feature: Make shards to own shard object[/-] [+]feature: Make shards to own shard object locally [/+] on Aug 21, 2026
  4. moved this from New to Done in kcpon Sep 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

kind/featureCategorizes issue or PR as related to a new feature.

Type

No type

Projects

  • Status
    Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions