it's the same "bug" than OOM-1559 but for dmaap-dr-node. Same solution should apply

You can see it only when dr-prov is started

20190104 michaelobrien dmaap is ok now - but requires a restart of the pod
update: a 2nd sequenced deploy (11 min between components) - dmaap is fully up on 3.0.0-ONAP - 4 x 32g vms

onap onap-dmaap-dbc-pg-0 1/1 Running 0 4h
onap onap-dmaap-dbc-pg-1 1/1 Running 0 4h
onap onap-dmaap-dbc-pgpool-c5f8498-8zbvh 1/1 Running 0 4h
onap onap-dmaap-dbc-pgpool-c5f8498-njnhq 1/1 Running 0 4h
onap onap-dmaap-dmaap-bus-controller-557dc8c59c-c4lpd 1/1 Running 0 4h
onap onap-dmaap-dmaap-dr-db-576f7968b8-r5s5q 1/1 Running 0 4h
onap onap-dmaap-dmaap-dr-node-7647f9d6d8-zrqfn 1/1 Running 0 4h
onap onap-dmaap-dmaap-dr-prov-f4d84869f-5hxvf 1/1 Running 0 4h
onap onap-dmaap-message-router-76f4799d-59nmp 1/1 Running 0 4h
onap onap-dmaap-message-router-kafka-56c7c546c-bjhpt 1/1 Running 3 4h
onap onap-dmaap-message-router-zookeeper-7d69b496bc-q55pg 1/1 Running 0 4h