When the dump process of a dump task pod terminates, the pod enters a 2/3 NotReady state, as both sidecar containers are still ready.
That state is detected by the job-sidecar-controller, in charge of exec ing into each sidecar pod and killing the PID 1.
We observe that it takes quite a while for the task pods to transition from the 2/3 Unready state to the 0/3 Terminating state:
mediawiki-angwikisource-sql-xml-angwikisource-dump-batch-0-7fodo5b 0/3 ContainerCreating 0 2s mediawiki-angwikisource-sql-xml-angwikisource-dump-batch-0-7fodo5b 0/3 ContainerCreating 0 6s mediawiki-angwikisource-sql-xml-angwikisource-dump-batch-0-7fodo5b 2/3 Running 0 7s mediawiki-angwikisource-sql-xml-angwikisource-dump-batch-0-7fodo5b 3/3 Running 0 8s mediawiki-angwikisource-sql-xml-angwikisource-dump-batch-0-7fodo5b 2/3 NotReady 0 23s mediawiki-angwikisource-sql-xml-angwikisource-dump-batch-0-7fodo5b 1/3 NotReady 0 45s mediawiki-angwikisource-sql-xml-angwikisource-dump-batch-0-7fodo5b 1/3 NotReady 0 49s mediawiki-angwikisource-sql-xml-angwikisource-dump-batch-0-7fodo5b 0/3 Completed 0 49s
I postulate the opinion that this is due to the fact that the job sidecar controller is CPU throttled.
We probably need to increase its CPU resources.