1.7.2 docs #211
1.7.2 docs #211
Conversation
| # ... | ||
| ``` | ||
|
|
||
| When the controller receives the above Pod update, it will prioritize the deletion process of Pods with the specified deletion label and ensure that the `maxUnavailable` limit is not exceeded. |
There was a problem hiding this comment.
it will prioritize the deletion process of Pods with the specified deletion label
-> it will trigger the deletion process of the pod with specified deletion label .
plz also comment that the pod will be rebuild by the workload if the replicas is not matched after deletion.
There was a problem hiding this comment.
I emphasize prioritizing deletion over updates because I want to highlight that deletion takes precedence.
I think "the pod will be rebuilt by the workload if the replicas are not matched after deletion" should perhaps be "The pod will be rebuilt by the workload if the ordinal is not reserved."
This is because even if the replicas do not match after deletion, the pod will still be rebuilt, and the pod with the highest ordinal will be deleted.
…current(wait review) Signed-off-by: Abner-1 <yuanyuxing.yyx@alibaba-inc.com>
prepare 1.7.2 docs, introduction of specified-pod is only added into current(wait review)