add corner case for dispath suspension proposal

Signed-off-by: changzhen <changzhen5@huawei.com>
This commit is contained in:
changzhen 2024-08-16 11:01:36 +08:00
parent 235ec911b1
commit b99fb638e1
1 changed files with 8 additions and 2 deletions

View File

@ -153,7 +153,7 @@ type WorkSpec struct {
} }
``` ```
A new ConditionType called `SuspendDispatching` is introduced to describe the distribution suspension status of the Work resource. Meanwhile, the system will also report events to record the suspension of resource distribution. A new ConditionType called `Dispatching` is introduced to describe the distribution suspension status of the Work resource. Meanwhile, the system will also report events to record the suspension of resource distribution.
### User usage example ### User usage example
@ -195,7 +195,7 @@ spec:
status: status:
conditions: conditions:
- lastTransitionTime: "2024-07-01T08:33:28Z" - lastTransitionTime: "2024-07-01T08:33:28Z"
message: resource distribution is in a pause state. message: Work dispatching is in a suspended state.
reason: SuspendDispatching reason: SuspendDispatching
status: "True" status: "True"
type: Dispatching type: Dispatching
@ -256,6 +256,12 @@ If, after synchronizing the new version of the resource to the member1 cluster,
Q&A: How to remove the annotation `propagation.karmada.io/instruction` from Work? It can be carried by the `Dispatching` field in the Work. Q&A: How to remove the annotation `propagation.karmada.io/instruction` from Work? It can be carried by the `Dispatching` field in the Work.
### Corner Case Consideration
1. Resource dispatching suspension does not block resource deletion.
When a user specifies through PropagationPolicy that a resource is in a dispatching suspension, and then performs a deletion operation with the intention of removing the resource, the resource will be deleted normally without blocking the deletion, thus preventing leftover resources in the member clusters.
### Test Plan ### Test Plan
#### UT #### UT