github.com/argoproj/argo-cd/v3@v3.2.1/test/e2e/testdata/syncwaves-prune-order/README.md (about)

     1  ## Test Scenario
     2  
     3  This test example is for testing the reverse pruning of resources with syncwaves during sync operation.
     4  
     5  Resource creation happens in below order
     6  - wave 0: sa & role
     7  - wave 1: rolebinding
     8  - wave 2: pod
     9  
    10  They are setup in such a way that the resources will be cleaned up properly only if they are deleted in the reverse order of creation i.e
    11  - wave 0: pod
    12  - wave 1: rolebinding
    13  - wave 2: sa & role
    14  
    15  If above delete order is not followed the pod gets stuck in terminating state due to a finalizer which is supposed to be removed by k8s container lifecycle hook on delete if delete order is correct.