I have remove the seed run command from the normal container execution (it is not triggered anymore on any pod/container restart).
I have however opted to use a Kubernetes Job which uses the same catalog container it just overrides the default CMD and instead runs the npm seed script. These jobs have to be manually triggered by re-applying the seed-job.yml to the cluster. If there is a previously finished job on the cluster you first have to remove it. This is why I have prepared a simple bash script which removes and runs the same job again.
I have remove the seed run command from the normal container execution (it is not triggered anymore on any pod/container restart). I have however opted to use a Kubernetes Job which uses the same catalog container it just overrides the default CMD and instead runs the npm seed script. These jobs have to be manually triggered by re-applying the
seed-job.ymlto the cluster. If there is a previously finished job on the cluster you first have to remove it. This is why I have prepared a simple bash script which removes and runs the same job again.