cloudhealth-collector pod gets restarted due to emptydir

[bbilali]

Currently there’s no limit for the amount of memory the emptydir can consume, according to kubernetes/kubernetes#119611 this may end up crashing the node as the memory limit is not being considered when using emptydir (the emptydir can consume all the memory of the node, resulting in other processes being killed). Setting the limit to half of the allocated memory should be fine.

[vmwclabot]

@bbilali, you must sign our contributor license agreement before your changes are merged. Click here to sign the agreement. If you are a VMware employee, read this for further instruction.

[vmwclabot]

@bbilali, we have received your signed contributor license agreement. The review is usually completed within a week, but may take longer under certain circumstances. Another comment will be added to the pull request to notify you when the merge can proceed.

[kscherme]

Thank you for your contribution! Our team will take a look in the next few days.

[gm-cht]

Good one! we never reached the scenario where this tmpfs becomes large by any standard. And all our Nodes are disk backed instead of memory..
Glad we have a fix this scenario! Thank you!

[kscherme]

Thank you for your patience! We are in contact with the Open Source team regarding your contributor license agreement and will get back to you once it is reviewed

[vmwclabot]

@bbilali, VMware has approved your signed contributor license agreement.