Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Replicator fails to delete orphaned copies on pod restart #357

Open
kavishdahekar opened this issue Nov 4, 2024 · 0 comments
Open

Replicator fails to delete orphaned copies on pod restart #357

kavishdahekar opened this issue Nov 4, 2024 · 0 comments
Labels

Comments

@kavishdahekar
Copy link

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

  1. create 100 destination namespaces with names destination-X where 1<=X<=100
  2. create source secret with replicator.v1.mittwald.de/replicate-to=destination-.* annotation
  3. wait for replicator to create copies of source secret in all 100 destination namespaces
  4. delete the source secret. replicator will now begin deleting all the 100 copies in the destination namespaces
  5. kill the replicator pods and wait for new pods to come up
  6. 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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant