You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
If the replicator pods are restarted when its still in the middle of deleting copies of a source secret that was deleted, the new pod does not carry over the operation and the remaining copies are left orphaned and are not deleted.
To Reproduce
create 100 destination namespaces with names destination-X where 1<=X<=100
create source secret with replicator.v1.mittwald.de/replicate-to=destination-.* annotation
wait for replicator to create copies of source secret in all 100 destination namespaces
delete the source secret. replicator will now begin deleting all the 100 copies in the destination namespaces
kill the replicator pods and wait for new pods to come up
new replicator pods do not cleanup the remaining copies in the destination namespaces
Expected behavior
Replicator pods should finish the deletion task and not leave orphaned copies around.
Environment:
Kubernetes version: v1.30.5
kubernetes-replicator version: v2.10.2
Additional context
n/a
The text was updated successfully, but these errors were encountered:
Describe the bug
If the replicator pods are restarted when its still in the middle of deleting copies of a source secret that was deleted, the new pod does not carry over the operation and the remaining copies are left orphaned and are not deleted.
To Reproduce
destination-X
where1<=X<=100
replicator.v1.mittwald.de/replicate-to=destination-.*
annotationExpected behavior
Replicator pods should finish the deletion task and not leave orphaned copies around.
Environment:
Additional context
n/a
The text was updated successfully, but these errors were encountered: