Skip to content

Product Fleet Operations — deployment

Target

This page describes intended behaviour or structure. No implementation is claimed unless a section is explicitly marked Current implementation or Evidence.

Host Modules Topologies
FleetOperationsHost 3 saas-default, hybrid

Shape

flowchart TB
    subgraph host [FleetOperationsHost · AKS · 2–4 replicas]
        INV[FleetInventoryService]
        RO[FleetRolloutService]
        INC[FleetIncidentService]
    end
    host --> SQL["(fleet-sql)"]
    host <--> DEL[DeliveryHost]
    host <--> RT[RuntimeCloudHost]
    host <--> OBS[ObservabilityHost]
    host <--> INT[IntegrationHost · paging · notifications]
    host <--> DE[DataEventFoundations · orders]
    host -. health via GW-07 .-> P1["(product A instances)"]
    host -. health via GW-07 .-> P2["(product B instances)"]
Hold "Alt" / "Option" to enable pan & zoom

Per topology

Topology Where the host runs Instances it operates Notes
saas-default the Factory's region products on Factory-managed and tenant environments in Azure default for D33
hybrid the Factory's region customer-hosted instances reached through their gateways and the hybrid Runtime Cloud profile paging and notifications through the customer's connectors
on-prem not deployed self-operated products only (inventoried through an exported manifest, later) D33 applies to ConnectSoft-operated products
hybrid-compute as saas-default as saas-default

Data and recovery

fleet-sql: RPO 15 min, RTO 4 h (D30); inventory re-derives from delivery and runtime cloud; rollouts and incidents resume from restored state; off-boardings resume from their order references. Retention: incidents and off-boardings 7 years; rollouts for the product's lifetime plus 7 years.

Ports and runtime

HTTPS 8140, gRPC 8142, silo 12140, gateway 31140 (messaging profile fleet). Secrets fleet-sql, messaging-transport from Key Vault with 90-day rotation.