Architecture

Understand why the operator behaves the way it does.

Architecture pages explain controller boundaries, lifecycle coordination, and the invariants the system depends on. Use this section when you need to reason about behavior, validate assumptions, review tradeoffs, or change the code safely.

Read the invariantsOpen component design

Use architecture when you need to

• understand the contracts the operator is trying to preserve
• see how controllers, managers, and shared services divide responsibility
• follow a lifecycle flow from tenant onboarding to day 2 operations
• connect internal behavior back to security posture and status semantics

Architecture routes

1. 01

   Operator invariants

   Lifecycle contracts and the assumptions the controller design depends on.

   Open
2. 02

   Component design

   See how the split-controller control plane, app layer, and manager boundaries work together.

   Open
3. 03

   Operation lifecycle coordination

   Understand the shared lock, retry, and phase-transition primitives behind backup, restore, and upgrade flows.

   Open
4. 04

   Lifecycle architecture

   Follow the operator from Day 0 provisioning through Day 2 operations and backup-driven recovery.

   Open

Related sections

Open securityArchitecture and security are tightly coupled through RBAC, admission, identity, and workload controls.Open referenceUse exact status and event semantics when you need to connect architecture back to observable behavior.Open OperateCompare the internal lifecycle design with the user-facing operating guides for upgrades, backups, and recovery.