You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/service-fabric/overview-managed-cluster.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,15 +13,15 @@ ms.date: 03/12/2024
13
13
14
14
Service Fabric managed clusters are an evolution of the Azure Service Fabric cluster resource model that streamlines your deployment and cluster management experience.
15
15
16
-
The Azure Resource Model (ARM) template for traditional Service Fabric clusters requires you to define a cluster resource alongside a number of supporting resources, all of which must be "wired up" correctly (upon deployment and throughout the lifecycle of the cluster) in order for the cluster and your services to function properly. In contrast, the encapsulation model for Service Fabric managed clusters consists of a single, *Service Fabric managed cluster* resource. All of the underlying resources for the cluster are abstracted away and managed by Azure on your behalf.
16
+
The Azure Resource Model (ARM) template for traditional Service Fabric clusters requires you to define a cluster resource alongside a number of supporting resources, These resources must be configured correctly for the cluster and your services to function properly. In contrast, the encapsulation model for Service Fabric managed clusters consists of a single, *Service Fabric managed cluster* resource. All of the underlying resources for the cluster are abstracted away and managed by Azure on your behalf.
17
17
18
18
**Service Fabric traditional cluster model**
19
19
![Service Fabric traditional cluster model][sf-composition]
In terms of size and complexity, the ARM template for a Service Fabric managed cluster is about 100 lines of JSON, versus some 1000 lines required to define a typical Service Fabric cluster:
24
+
In terms of size and complexity, the ARM template for a Service Fabric managed cluster is about 100 lines of JSON, versus some 1,000 lines required to define a typical Service Fabric cluster:
25
25
26
26
| Service Fabric resources | Service Fabric managed cluster resources |
27
27
|----------|-----------|
@@ -49,7 +49,7 @@ Service Fabric managed clusters provide a number of advantages over traditional
49
49
**Best practices by default**
50
50
- Simplified reliability and durability settings
51
51
52
-
There is no additional cost for Service Fabric managed clusters beyond the cost of underlying resources required for the cluster, and the same Service Fabric SLA applies for managed clusters.
52
+
There's no extra cost for Service Fabric managed clusters beyond the cost of underlying resources required for the cluster, and the same Service Fabric Service Leval Agreement (SLA) applies for managed clusters.
53
53
54
54
> [!NOTE]
55
55
> There is no migration path from existing Service Fabric clusters to managed clusters. You will need to create a new Service Fabric managed cluster to use this new resource type.
@@ -64,15 +64,15 @@ Service Fabric managed clusters are available in both Basic and Standard SKUs.
64
64
| Feature | Basic | Standard |
65
65
| ------- | ----- | -------- |
66
66
| Network resource (SKU for [Load Balancer](../load-balancer/skus.md), [Public IP](../virtual-network/ip-services/public-ip-addresses.md)) | Basic | Standard |
The capabilities of managed clusters will continue to expand. See [managed cluster configuration options documentation](how-to-managed-cluster-configuration.md) or managedClusters [Bicep & ARM templates](/azure/templates/microsoft.servicefabric/allversions) for more information.
75
+
See [managed cluster configuration options documentation](how-to-managed-cluster-configuration.md) or managedClusters [Bicep & ARM templates](/azure/templates/microsoft.servicefabric/allversions) for more information.
In this step, you will create a Service Fabric managed cluster using the New-AzServiceFabricManagedCluster PowerShell command. The following example creates a cluster named myCluster in the resource group named myResourceGroup. This resource group was created in the previous step in the eastus2 region.
65
+
In this step, you create a Service Fabric managed cluster using the New-AzServiceFabricManagedCluster PowerShell command. The following example creates a cluster named myCluster in the resource group named myResourceGroup. This resource group was created in the previous step in the eastus2 region.
66
66
67
67
For this step, provide your own values for the following parameters:
68
68
69
69
***Cluster Name**: Enter a unique name for your cluster, such as *mysfcluster*.
70
-
***Admin Password**: Enter a password for the admin to be used for RDP on the underlying VMs in the cluster.
71
-
***Client Certificate Thumbprint**: Provide the thumbprint of the client certificate that you would like to use to access your cluster. If you do not have a certificate, follow [set and retrieve a certificate](../key-vault/certificates/quick-create-portal.md) to create a self-signed certificate.
72
-
***Cluster SKU**: Specify the [type of Service Fabric managed cluster](overview-managed-cluster.md#service-fabric-managed-cluster-skus) to deploy. *Basic* SKU clusters are meant for test deployments only, and do not allow for node type addition or removal.
70
+
***Admin Password**: Enter a password for the admin to be used for Remote Desktop Protocol (RDP) on the underlying VMs in the cluster.
71
+
***Client Certificate Thumbprint**: Provide the thumbprint of the client certificate that you would like to use to access your cluster. If you don't have a certificate, follow [set and retrieve a certificate](../key-vault/certificates/quick-create-portal.md) to create a self-signed certificate.
72
+
***Cluster SKU**: Specify the [type of Service Fabric managed cluster](overview-managed-cluster.md#service-fabric-managed-cluster-skus) to deploy. *Basic* SKU clusters are meant for test deployments only, and don't allow for node type addition or removal.
### Add a primary node type to the Service Fabric managed cluster
84
84
85
-
In this step, you will add a primary node type to the cluster that you have just created. Every Service Fabric cluster must have at least one primary node type.
85
+
In this step, you add a primary node type to the cluster that you created. Every Service Fabric cluster must have at least one primary node type.
86
86
87
87
For this step, provide your own values for the following parameters:
0 commit comments