Skip to content

fix: update VirtualClusterManager → VirtualClusterRegistry in proposal 083 - #3

Closed
SamBarker wants to merge 1 commit into
Uzziee:hot-reload-proposalfrom
SamBarker:fix/083-vcr-naming
Closed

fix: update VirtualClusterManager → VirtualClusterRegistry in proposal 083#3
SamBarker wants to merge 1 commit into
Uzziee:hot-reload-proposalfrom
SamBarker:fix/083-vcr-naming

Conversation

@SamBarker

Copy link
Copy Markdown

VirtualClusterManager was renamed to VirtualClusterRegistry in the main codebase yesterday. This PR updates all references in proposal 083 accordingly.

Changes:

  • Replace VirtualClusterManager with VirtualClusterRegistry throughout the proposal prose
  • Fix the orchestration pipeline diagram, which incorrectly labelled VirtualClusterRegistry as a per-VC construct — it is one registry for all clusters
  • Untangle the rejected alternative entry, which became confusing after the rename: the rejected thing was the separate orchestrator class shape (previously called VirtualClusterManager), not VirtualClusterRegistry itself

…proposal 083

VirtualClusterManager was renamed to VirtualClusterRegistry in the main
codebase. Update all references in the proposal accordingly, and fix the
orchestration pipeline diagram which incorrectly described VirtualClusterRegistry
as a per-VC construct (it is one registry for all clusters).

Also clarifies the rejected alternative entry, which was tangled by the rename:
the rejected thing was the separate VirtualClusterManager orchestrator shape,
not VirtualClusterRegistry itself.

Signed-off-by: Sam Barker <sam.barker@example.com>
Signed-off-by: Sam Barker <sam@quadrocket.co.uk>
@SamBarker SamBarker closed this May 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant