mirror of
https://github.com/hanzoai/deploy.git
synced 2026-10-07 08:44:50 +00:00
Siddhesh GhadiandGitHub
a02677cdd0
* Add e2e & doc for prune order during sync Signed-off-by: Siddhesh Ghadi <[email protected]> * Point gitops-engine to fork with reverse prune changes Signed-off-by: Siddhesh Ghadi <[email protected]> * Fix ci linting failures Signed-off-by: Siddhesh Ghadi <[email protected]> * Update gitops-engine commit ref Signed-off-by: Siddhesh Ghadi <[email protected]> --------- Signed-off-by: Siddhesh Ghadi <[email protected]>
Test Scenario
This test example is for testing the reverse pruning of resources with syncwaves during sync operation.
Resource creation happens in below order
- wave 0: sa & role
- wave 1: rolebinding
- wave 2: pod
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
- wave 0: pod
- wave 1: rolebinding
- wave 2: sa & role
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.