Created Resources

Once the deployment is initiated, the Marketplace will start creating the required resources for the cluster, starting with the managed resource group where all of the resources are deployed. The resources created include the following:

• Alerts - We set up a few alerts to identify issues in the cluster: server down, maintenance notification from Azure, VM shutdown (deallocate), and VM delete.
• App Insights - The cluster nodes and cluster app functions write logs and events to the app insights (traces table).
• Cluster VMSS - Scale set running the cluster instances. Note that in a MultiAZ deployment, there will be a VMSS for each AZ (for a total of three).
• Function App Plan - Plan that holds the various maintenance and support tools.
• KeyVault Store - This is where the deployment will store all of the secrets required for the cluster. For example, JWTs for API services and various certificates.
• Loadbalancer (Internal) - API and Discovery Service LB with an internal VIP, so that clients can connect to the required services (note that data path/NVMe commands are performed directly to the instances and not via the LB).
• Loadbalancer (Outbound) - For Azure API services.
• Public IP - Public IP for the outbound traffic to Azure Services (used by the Outbound LB).
• Security Group - NIC-level NSG to limit the access to the instances only to the required ports.
• Storage Account - Storage account used by the cluster's function apps.
• User-managed-identity - Identity to access the VMSS information and the KeyVault to store and read secrets.