Build Service Fabric cluster configs with node types, reliability levels, durability, placement properties, and fabric settings.
Build Service Fabric cluster configs with node types, reliability levels, durability, placement properties, and fabric settings.
Required Fields
clusterNameresourceGroupreliabilityLevelnodeTypesnodeTypes[0].namenodeTypes[0].vmInstanceCountnodeTypes[0].vmSizeOutput will appear here...The builder validates that clusterName, resourceGroup, reliabilityLevel, nodeTypes, and the first node type's name/vmInstanceCount/vmSize all resolve before accepting the JSON as a valid cluster definition, the fields Service Fabric needs to know the cluster's reliability requirements and its node type topology; it can't verify the specified vmInstanceCount actually satisfies the chosen reliabilityLevel's documented minimum, that check happens only against the live Service Fabric resource provider at cluster creation.
Build an Azure Service Fabric cluster with node types (isPrimary distinguishing the system-services-hosting primary node type from worker node types), reliabilityLevel governing the minimum node count Service Fabric enforces for cluster quorum safety, and durabilityLevel controlling how gracefully the cluster handles a VM Scale Set-level infrastructure job (like an OS update) on that node type. reliabilityLevel Platinum, Gold, Silver, Bronze aren't just labels, each maps to a specific minimum primary node type instance count Service Fabric requires to guarantee quorum during simultaneous node failures, setting a reliabilityLevel your node type's actual vmInstanceCount doesn't satisfy is rejected at cluster creation, not silently accepted with reduced guarantees.
Always verify the primary node type's vmInstanceCount meets the minimum required for the chosen reliabilityLevel before attempting cluster creation, the specific minimums are documented per level and checking them upfront avoids a failed deployment.
durabilityLevel matters specifically for VM sizes and SKUs that support the coordinated infrastructure-maintenance drain, verify your chosen vmSize actually supports the durability level you're requesting, not every VM size supports every durability tier.
ClusterProtectionLevel EncryptAndSign is the appropriate baseline for any production cluster, a lower protection level trades security for a marginal performance benefit that's rarely worth it outside of a constrained dev/test scenario.
Cluster creation is rejected outright, each reliability level has a documented minimum primary node type instance count (increasing from Bronze through Platinum) required to guarantee the cluster can maintain quorum during simultaneous node failures, Azure validates this at creation time rather than silently accepting an under-provisioned configuration with weaker guarantees than requested.
reliabilityLevel governs Service Fabric's own replica placement and quorum guarantees for its system services. durabilityLevel is about coordination with the underlying Azure infrastructure, specifically, whether Service Fabric can tell the VM Scale Set 'wait, let me safely move workloads off this node before you reboot it for an OS update', without adequate durability support, an infrastructure-initiated maintenance event can take down multiple nodes in a node type simultaneously with no coordinated drain.
Yes, and this is common, the primary node type hosts Service Fabric's own system services and often uses a more standard, reliable VM size, while worker node types (like nt-worker in the example, using a larger Standard_D8s_v5) can be sized specifically for the actual application workload's resource needs, independent of the primary node type's sizing.
Was this tool helpful?
Disclaimer: This tool runs entirely in your browser. No data is sent to our servers. Always verify outputs before using them in production. AWS, Azure, and GCP are trademarks of their respective owners.