Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

KCP Sharding #18751

Open
1 task
janmedrek opened this issue Sep 25, 2024 · 1 comment
Open
1 task

KCP Sharding #18751

janmedrek opened this issue Sep 25, 2024 · 1 comment
Assignees
Labels
Epic lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@janmedrek
Copy link
Contributor

Description

The KCP sharding concept should be introduced to allow us to scale KCP clusters.

The whole concept revolves around providing multiple K8S clusters, this way the Kube API server will not get stuffed with all the necessary resources to serve SKR lifecycle functionalities.

The following questions would need to be answered:

  • Should KEB be the singleton component responsible for the round-robin dispatching over multiple KCP clusters?
  • Which operators should be "sharded"? Naturally, KLM should pop up on that list, what about KIM/other KCP components?
  • Should we set up separate Gardener projects for specific KCP shards?

Acceptance Criteria (TBD)

  • KCP sharding introduced

Context

Problem
With the increasing number of resources that need to be reconciled, problems with performance occur. Some sort of horizontal scaling needs to be introduced as operators serving such resources cannot be scaled indefinitely.

@janmedrek janmedrek added the Epic label Sep 25, 2024
@janmedrek janmedrek self-assigned this Sep 25, 2024
@janmedrek janmedrek changed the title KCP Sharding [EPIC] KCP Sharding Oct 21, 2024
Copy link

This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs.
Thank you for your contributions.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Epic lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

1 participant