HV-VES Pod recovery when config-fetch fails

We noticed strange behavior of HV-VES pod in Guilin release.
After 5 days from installation pod become unhealthy.

ubuntu@onap-5915-rke-node:~$ kubectl get pods -n onap |  grep hv-ves
dep-dcae-hv-ves-collector-d8b6f56d4-dh67n         1/2     Running                 0          12d

In attachment:
hv-ves.2020-10-28.0.log log from day when ONAP has been deployed
hv-ves.2020-11-02.0.log log from day when HV-VES pod become unhealthy.

POD restart helps in order to make it healthy