Multi-Release-Epic: Sharding #1225
Labels
area/sharding
Issues or PRs related to sharding changes
epic
Represents a larger feature with multiple stories
feature-completion
milestone-blocker
Blocks closing out a milestone
Milestone
Demo Objective
X
in the parent workspaceparent(X)
on the shard the workspaceX
lives on.Action Items
========= WIP, but won't merge by v0.6 =========
with informer merging, andhow to enable existing controller to work with second informer========= up to here for v0.7 ==========
add identities configmap in system:shard @p0lyn0mial
implement replication controller / cache server
cmd/cache-server
andpkg/cache/server/{config.go,server.go}
andpkg/cache/server/options
plumbing (cache-server scaffolding #1790)apiextensions-apiserver
and wire CRD lister similar to today'spkg/server/apiextensions.go
with at least APIExports and APIResourceSchemaskcp/pkg/virtual/apiexport/schemas/apis.go
Line 36 in 8d2ed6a
========= up to here for v0.8 ==========
implement replication controller / cache server (continued)
/registry/group/cache:resource:identity:shard/…
(cache-server: adds WithShardScope HTTP filter #1841)/services/cache/shards/*/clusters/*
(🌱 cache: expose the cache-server under "/services/cache" path #1961)/services/cache/shards/{shard-name}/clusters/{cluster-name}
(🌱 cache: expose the cache-server under "/services/cache" path #1961)kcp
binary. (🌱 cache: small refactor to make wiring into kcp easier #1949, 🌱 cache: moves common HTTP handlers to a shared pkg #1947, 🌱 Wire the cache server into the kcp server #1954)--cache-url
intokcp
, defaulting to localhost. (🌱 kcp: add flags related to the cache server #1970)authorization
subscription model
data removal
unused resources could be automatically removed
shard management, a few loose ideas:
what will decide when a new shard needs to be created ?
which cluster it gets deployed to ?
making other shards aware of the new shard ?
(in parallel, best effort) add some other controller(s), e.g. ClusterWorkspaces
[ ] wire informer both ways @p0lyn0mial
[ ] start the second informer (aka.
TemporaryRootShardKcpSharedInformerFactory
) in a dedicated post-start-hook @p0lyn0mialTesting
Backlog:
Stories
Context
The text was updated successfully, but these errors were encountered: