rebase and fix

Signed-off-by: melserngawy <[email protected]>
open-cluster-management-io · Nov 15, 2023 · 9601b01 · 9601b01
1 parent 52e1f06
commit 9601b01
Showing 1 changed file with 4 additions and 2 deletions.
diff --git a/content/en/concepts/manifestworkreplicaset.md b/content/en/concepts/manifestworkreplicaset.md
@@ -41,7 +41,7 @@ spec:
         rolloutType: ProgressivePerGroup
         progressivePerGroup:
           progressDeadline: 10m
-          maxFailures: 5%
+          maxFailures: 2
   manifestWorkTemplate:
     deleteOption:
       propagationPolicy: SelectivelyOrphan
@@ -103,8 +103,10 @@ The manifestWorkReplicaSet Summary aggregate the placementSummary showing the to
 
 The manifestWorkReplicaSet has three status conditions; 
 1. **PlacementVerified** verify the placementRefs status; not exist or empty cluster selection. 
-1. **ManifestWorkApplied** verify the created manifestWork status; applied, progressing, degraded or available.
 1. **PlacementRolledOut** verify the rollout strategy status; progressing or complete.
+1. **ManifestWorkApplied** verify the created manifestWork status; applied, progressing, degraded or available.
+
+The manifestWorkReplicaSet determine the ManifestWorkApplied condition status based on the resource state (applied or available) of each manifestWork.
 
 Here is an example.