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/faq-managed-cluster.yml
+9-9Lines changed: 9 additions & 9 deletions
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ metadata:
7
7
author: tomvcassidy
8
8
ms.service: service-fabric
9
9
services: service-fabric
10
-
ms.date: 07/11/2022
10
+
ms.date: 03/12/2024
11
11
title: Service Fabric managed clusters frequently asked questions
12
12
summary: Here are some frequently asked questions (FAQs) and answers for Service Fabric managed clusters.
13
13
@@ -27,20 +27,20 @@ sections:
27
27
- question: |
28
28
Can I do an in-place migration of my existing Service Fabric cluster to a managed cluster resource?
29
29
answer: |
30
-
No. You will need to create a new Service Fabric cluster resource to use the new Service Fabric managed cluster resource type.
30
+
No, you need to create a new Service Fabric cluster resource to use the new Service Fabric managed cluster resource type.
31
31
32
32
- question: |
33
33
Is there an additional cost for Service Fabric managed clusters?
34
34
answer: |
35
-
No. There is no additional cost associated with a Service Fabric managed cluster beyond the cost of the underlying compute, storage, and networking resources that are required for the cluster.
35
+
No, there's no additional cost associated with a Service Fabric managed cluster beyond the cost of the underlying compute, storage, and networking resources that are required for the cluster.
36
36
37
37
- question: |
38
38
Is there a new SLA introduced by the Service Fabric managed cluster resource?
39
39
answer: |
40
40
The SLA doesn't change from the current Service Fabric resource model.
41
41
42
42
- question: |
43
-
What is the difference between a Basic, and Standard SKU cluster?
43
+
What's the difference between a Basic, and Standard SKU cluster?
44
44
answer: |
45
45
Basic SKU clusters are intended to be used for testing and pre production environments with support for minimal configuration change. A Standard SKU cluster allows users to configure the cluster to specifically meet their needs. For more information, see [Service Fabric managed cluster SKUs](./overview-managed-cluster.md#service-fabric-managed-cluster-skus).
46
46
@@ -64,27 +64,27 @@ sections:
64
64
- question: |
65
65
Can I change the Microsoft Entra tenant after initial deployment?
66
66
answer: |
67
-
No. At this time you would need to create a new Service Fabric managed cluster resource.
67
+
No, you need to create a new Service Fabric managed cluster resource.
68
68
69
69
- question: |
70
70
Can I transfer my subscription to a different Microsoft Entra tenant?
71
71
answer: |
72
-
No. At this time you would need to create a new Service Fabric managed cluster resource after the subscription has been transferred to a different Microsoft Entra tenant.
72
+
No, you need to create a new Service Fabric managed cluster resource after the subscription has been transferred to a different Microsoft Entra tenant.
73
73
74
74
- question: |
75
75
Can I move/migrate my cluster between Microsoft Entra tenants?
76
76
answer: |
77
-
No. At this time you would need to create a new Service Fabric managed cluster resource under the new tenant.
77
+
No, you need to create a new Service Fabric managed cluster resource under the new tenant.
78
78
79
79
- question: |
80
80
Can I move/migrate my cluster between subscriptions?
81
81
answer: |
82
-
No. At this time you would need to create a new Service Fabric managed cluster resource under the new subscription.
82
+
No, you need to create a new Service Fabric managed cluster resource under the new subscription.
83
83
84
84
- question: |
85
85
Can I move/migrate my cluster or cluster resources to other resource groups or rename them?
86
86
answer: |
87
-
No. At this time you would need to create a new Service Fabric managed cluster resource under the new resource group/name.
87
+
No, you need to create a new Service Fabric managed cluster resource under the new resource group/name.
Copy file name to clipboardExpand all lines: articles/service-fabric/how-to-managed-cluster-maintenance-control.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,8 +2,8 @@
2
2
title: Configure maintenance control for Service Fabric managed cluster
3
3
description: Learn how to configure maintenance control for Service Fabric managed cluster
4
4
ms.topic: how-to
5
-
ms.author: ashank
6
-
author: ashank
5
+
ms.author: tomcassidy
6
+
author: tomvcassidy
7
7
ms.service: service-fabric
8
8
services: service-fabric
9
9
ms.date: 03/12/2024
@@ -13,7 +13,7 @@ ms.date: 03/12/2024
13
13
Service Fabric managed clusters have multiple background operations that are necessary to the keep all the cluster updated, thus ensuring security and reliability. Even though these operations are critical, but executing in the background can result in the service replica to move to a different node. This failover results in
14
14
undesired and unnecessary interruptions, if the maintenance operation executes during the peak business hours. With the support for MaintenanceControl in Service Fabric managed clusters, customers would be able to define a recurring (daily, weekly, monthly) and custom maintenance window for their SFMC cluster resource,
15
15
as per their needs. All background maintenance operations will be allowed to execute only during this maintenance window. MaintenanceControl is applicable to these background operations:
16
-
* Automatic OSUpgrade
16
+
* Automatic OS Upgrade
17
17
* Automatic extension upgrade
18
18
* Automatic SF runtime version updates
19
19
* Automatic cluster certificate update
@@ -27,7 +27,7 @@ as per their needs. All background maintenance operations will be allowed to exe
27
27
28
28
## How does MaintenanceControl work for SFMC
29
29
* Customers need to define a maintenance configuration that contains the schedule and the recurrence rule for the maintenance window, by creating a maintenance configuration resource with the maintenance RP. [More details](../virtual-machines/maintenance-and-updates.md)
30
-
*Using this maintenance configuration, an assignment resource is created to assign the maintenance configuration to the SFMC cluster resource.
30
+
*With this maintenance configuration, an assignment resource is created to assign the maintenance configuration to the SFMC cluster resource.
31
31
* on the creation of the assignment resource, the maintenance RP notifies the ServiceFabric RP about the link and maintenance control is then enabled on the SFMC cluster. All background maintenance operations are blocked outside the maintenance window.
32
32
* Whenever the maintenance window is activated as per the schedule in the maintenance configuration, the maintenance RP notifies the ServiceFabric RP that activates the maintenance window on corresponding SFMC cluster. All background operations are allowed to execute during this window.
0 commit comments