docs: Multi-region workload scheduling design#106
Open
scotwells wants to merge 4 commits into
Open
Conversation
scotwells
changed the title
Defines the Karmada-based federation architecture for compute workload scheduling. Covers control plane topology, resource locations, creation and deletion flows, instance visibility, operator changes, auto scaling model, and namespace mapping conventions. Resolves #85 Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
scotwells
force-pushed
the
docs/issue-85-karmada-federation-design
branch
from
a85976d to
8de2c6f
Compare
scotwells
force-pushed
the
docs/issue-85-karmada-federation-design
branch
from
08a5471 to
8de2c6f
Compare
scotwells
changed the title
5 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
As Datum expands to more cities, the platform needs to schedule and route workloads efficiently without relying on a single central coordinator. This document defines the architecture for distributing scheduling across regional clusters, so workloads reach their target locations faster, scaling decisions happen locally at each site, and the platform stays available even when parts of the control plane are temporarily unreachable.
From a user perspective, nothing changes — city-code targeting and instance visibility work exactly as before.
Test plan
Closes #85