fix(deployment): suspend loculus-revoke-and-regroup-cronjob #2862
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
resolves #
preview URL: https://stop-revoke-cronjob.loculus.org/
Summary
Although
loculus-revoke-and-regroup-cronjob
was scheduled to a non-existent time it was still being startedby argocd, this caused concurrent ingest and duplication of ingested sequences.Edit from Theo:
I suspect it was being started by kubernetes, not argocd
Screenshot
PR Checklist