Azure Stack Hub
Customer-operated integrated system of 4 to 16 servers running Azure services in your own datacenter, connected or disconnected.
- Provider
- azure
- Kind
- Edge appliance
- Category
- Compute
| property | type | values | required | kind default | this component |
|---|---|---|---|---|---|
| cloudManaged | boolean | — | no | true | ▸ false |
| connectivity | enum | connected | intermittent | disconnected | no | — | inherited |
| deploymentModel | enum | connected | disconnected | no | — | inherited |
| formFactor | enum | rack | ruggedized | virtual | no | — | ▸ rack |
| identityProvider | enum | entra-id | ad-fs | no | — | inherited |
| localStorageGib | integer | — | no | — | inherited |
| managed | boolean | — | no | false | inherited |
| offlineMode | boolean | — | no | — | inherited |
| scaleUnitMaxServers | integer | — | no | 16 | inherited |
| scaleUnitMinServers | integer | — | no | 4 | inherited |
Every rule whose selector covers this component's kind or its category. Whether a rule fires depends on the design: its properties, its edges and its groups.
stateful-node-without-zone-redundancy
A stateful compute node pinned to exactly one availability zone disappears with that zone, and its state goes with it. Nodes inside a cell are exempt, because there the cell is deliberately single-zone and redundancy comes from the other cells.
- — all of these hold:
- — the node's `stateless` is false
- — the node sits inside exactly 1 availability-zone group
- — this does not hold:
- — the node sits inside at least one cell group
nodes:
- { id: "stack-hub", component: "azure-stack-hub" }Cloud Storage Gatewayalibaba-cloud-storage-gatewaySmart Access Gatewayalibaba-smart-access-gatewayAWS Backup gatewayaws-backup-gatewayAmazon EKS Anywhereaws-eks-anywhereAmazon FSx File Gatewayaws-fsx-file-gatewayAWS IoT Greengrassaws-iot-greengrassAWS IoT Greengrass Version 1aws-iot-greengrass-v1AWS Outposts rackaws-outpostsAWS Storage Gatewayaws-storage-gatewayAKS Edge Essentialsazure-aks-edge-essentialsAzure Data Box Gatewayazure-data-box-gatewayAzure IoT Edgeazure-iot-edgeAzure IoT Operationsazure-iot-operationsAzure Localazure-localOn-premises data gatewayazure-on-premises-data-gatewayAzure Operator Nexusazure-operator-nexusAzure Stack Edgeazure-stack-edgeCloudflare One Appliancecloudflare-one-appliancebalenabalenaGeneric edge applianceedge-applianceKubeEdgekubeedgeOpenYurtopenyurtGoogle Distributed Cloud air-gappedgoogle-distributed-cloud-air-gappedGoogle Distributed Cloud connectedgoogle-distributed-cloud-connectedGateway Applianceibm-gateway-applianceOracle Compute Cloud@Customeroci-compute-cloud-at-customerOracle Compute Cloud@Customer Isolatedoci-compute-cloud-at-customer-isolatedOracle Private Cloud Applianceoci-private-cloud-applianceOracle Roving Edge Infrastructureoci-roving-edgeOracle Roving Edge Classicoci-roving-edge-classic
# yaml-language-server: $schema=../../schema/component.schema.json # Azure Stack Hub: an integrated system of 4 to 16 servers (a scale unit) run in the customer's # datacenter, connected to Azure or fully disconnected ("Azure Stack Hub Overview"). # The customer owns and operates the appliance through its own admin portal, not Azure. schemaVersion: "1" type: "component" id: "azure-stack-hub" kind: "edge-appliance" provider: "azure" docs: "https://learn.microsoft.com/en-us/azure-stack/operator/azure-stack-overview" defaults: formFactor: "rack" cloudManaged: false properties: deploymentModel: type: "enum" values: ["connected", "disconnected"] identityProvider: type: "enum" values: ["entra-id", "ad-fs"] scaleUnitMinServers: type: "integer" default: 4 scaleUnitMaxServers: type: "integer" default: 16