Hi there,
I’m facing with a problem where the replicaset searches for the kubernetes cronjob’s pod (already terminated). We have a small container runs by a schedule do execute mongodump, but for some reason it joins to the replicaset and this generates a lots of log messages in the replicaset while trying to execute heartbeat checks and reconnecting to this pod.
Is there anything i miss here to avoid that the mongodump pod joins to the replicaset?
Both the replicaset and the pod deployed to the same namespace.
Expected behaviour:
The cronjob executed and the mongodump pod runs, without joining the replicaset.
Thanks in advance!