Skip to content

epic: Setup kcp Production Ready #68

Closed
2 of 2 issues completed
Closed

Description

@mirzakopic

Description

As part of running KCP internally at SAP, but also as research for setting it up and providing guidelines either in Platform Mesh or to other teams (such as at SAP), we need to understand what is the optimal way to setup kcp that can:

  • Scale to a large number of workspaces
  • Use ETCD droid as ETCD storage for kcp
  • Backup scenarios with ETCD
  • Sharding configurations for scaling

Objectives

Simple, if I were to setup a KCP for a large usage with 10,000+ accounts (ie workspaces), what would that be like?

What we have seen so far is that as you add more workspaces (empty ws, the response time increases). But we didnt fine tune that instance.

Research results from Lukas can be used here to understand the initial scenario of scaling.


Part of this is also exploratory, to understand what potential bottlenecks there might be and raise ticket for issues that we find. This would help us but also the wider KCP community.

Demo Required

Yes

Demo Steps

Hardware will be provided by SAP for testing and a playground with production ready resources.

To get started, talk to Mirza

Activity

  1. added theissue type on Sep 3, 2025
  2. self-assigned this
    on Oct 2, 2025
  3. moved this from Backlog to In Progress in Platform Mesh & Kube Projects - Backlogon Oct 2, 2025
  4. added this to the pm v0.1 milestone on Oct 29, 2025
  5. changed the title [-]epic: Setup KCP Production Ready[/-] [+]epic: Setup kcp Production Ready[/+] on Jun 15, 2026
  6. moved this from Done to Demo'd in OpenMesh - Backlogon Jul 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions