kubedex fails with StatusCode.RESOURCE_EXHAUSTED Received message larger than max

[bergerx]

in some of our clusters kubedex fails with the following error.

kubectl logs -n monitoring msa-monitoring-kubedex-exporter-5555975f7-hdhwv
<_Rendezvous of RPC that terminated with:
	status = StatusCode.RESOURCE_EXHAUSTED
	details = "Received message larger than max (5308389 vs. 4194304)"
	debug_error_string = "{"created":"@1554216457.448112296","description":"Error received from peer","file":"src/core/lib/surface/call.cc","file_line":1099,"grpc_message":"Received message larger than max (5308389 vs. 4194304)","grpc_status":8}"
>
<_Rendezvous of RPC that terminated with:
	status = StatusCode.RESOURCE_EXHAUSTED
	details = "Received message larger than max (5308389 vs. 4194304)"
	debug_error_string = "{"created":"@1554216460.004088903","description":"Error received from peer","file":"src/core/lib/surface/call.cc","file_line":1099,"grpc_message":"Received message larger than max (5308389 vs. 4194304)","grpc_status":8}"
>
<_Rendezvous of RPC that terminated with:
	status = StatusCode.RESOURCE_EXHAUSTED
	details = "Received message larger than max (5308389 vs. 4194304)"
	debug_error_string = "{"created":"@1554216462.964069445","description":"Error received from peer","file":"src/core/lib/surface/call.cc","file_line":1099,"grpc_message":"Received message larger than max (5308389 vs. 4194304)","grpc_status":8}"