Manage Infrastructures
Use /admin/common/infrastructures to verify infrastructure registry and control-plane sync health.
What this page is for
- Confirm infra metadata (
name,region, API base URLs, status) - Observe Common synchronization health from each infra
- Trigger authz snapshot sync when drift or lag appears
Common sync status
Each row includes a Common sync summary:
authz <age>: staleness of authz snapshot syncrepos <age>: staleness of repo provisioning syncfail <n>: consecutive failures for that sync track
If ages increase unexpectedly or failure counters rise, investigate infra-to-Common connectivity immediately.
Safe operations
- Verify
api_base_urlis browser-reachable for operators. - Verify
service_api_base_urlis valid for service-to-service routing where used. - Keep infrastructure
statusaccurate (ACTIVEwhen usable). - Use
Sync nowonly when you need deterministic refresh after control-plane changes.
Failure triage
errorin sync cell usually means auth or network failure from infra to Common.- Persistent repo sync failures often correlate with tenant repos stuck in
PROVISIONING. - Fix environment wiring first, then re-run sync.