updated

Author: youngbupark

enhancements/sig-architecture/227-manifestworkreplicaset-rollout-plugin/README.md

@@ -143,19 +143,21 @@ sequenceDiagram
           Note over Work, PluginServer: Start automatic abort
           Work->>Work: Set .status.abort to true
           Work->>Work: Set .status.abortedTime to the current time
+          Work->>Work: Update the desired revision to `.status.currentRevision`
         end
         alt is normal rollout? (.status.abort == false)
           Work->>PluginServer: (NEW) ProgressRollout()
+          PluginServer-->>Work: OK
         else is abort operation? (.status.abort == true)
           Work->>PluginServer: (NEW) ProgressAbort()
+          PluginServer-->>Work: OK
         end
-        PluginServer-->>Work: OK
         alt is normal rollout? (.status.abort == false)
           Note over Work, PluginServer: Normal Rollout
           loop clusterToRollout clusters
               Work->>PluginServer: (NEW) BeginRollout()
               PluginServer-->>Work: OK
-              Work->>PluginServer: (NEW) MutateManifestwork()
+              Work->>PluginServer: (NEW) MutateManifestwork(the desired revision)
               PluginServer-->>Work: (NEW) Return mutated Manifestwork resource
               Work->>APIServer: Apply the mutated ManifestWork resource to the current cluster
           end
@@ -164,7 +166,7 @@ sequenceDiagram
           loop existing clusters (updated clusters)
               Work->>PluginServer: (NEW) BeginAbort()
               PluginServer-->>Work: OK
-              Work->>PluginServer: (NEW) MutateManifestwork()
+              Work->>PluginServer: (NEW) MutateManifestwork(the desired revision)
               PluginServer-->>Work: (NEW) Return mutated Manifestwork resource
               Work->>APIServer: Apply the mutated ManifestWork resource to the current cluster
           end
@@ -176,7 +178,6 @@ sequenceDiagram
 
 This workflow introduces four new plugin API calls:
 
-
 * `BeginRollout()`: Called before applying the ManifestWork to a target cluste to roll out new revision, allowing the plugin to perform any necessary preparations.
 * `ProgressRollout()`: Called during every reconciliation loop to report the current rollout status to the plugin.
 * `ValidateRolloutCompletion()`: Called after the `Progressing` condition on the target cluster's ManifestWork becomes False. This hook enables post-rollout testing before the status is set to Succeeded. For example, the plugin could use this call to create a new ManifestWork that runs a Kubernetes Job for verification. **Note that this hook must be called within the `ProgressDeadline` timeout.**