ADR for Servala Control Plane Architecture #1
No reviewers
Labels
No labels
bug
change
duplicate
enhancement
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: servala/documentation#1
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "adr/control-plane"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
LGTM
Just a few nitpicks about the role of the control panel.
@ -16,3 +64,4 @@## DecisionWe've decided to move away from the split control plane architecture and instead let the Servala Portal handle orchestration.The portal did the orchestration already. It had to tell the control plane which service clusters should get used.
@ -21,0 +88,4 @@#### What We're Trading OffThe Portal becomes critical infrastructure for orchestration. If it's down, orchestration stops.This statement is also true with split architecture, as the control panel still did the orchestration.
Besides the comments from @simon.beck and my small edit in
77a0d02d2e- LGTM77a0d02d2etodf380a4bd6df380a4bd6tocf24cec7b7