You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Activity
[-]epic: Setup KCP Production Ready[/-][+]epic: Setup kcp Production Ready[/+]