I'm not sure if this is what fixed the issue for me, but I was running into a similar error, and after we upgraded our kubernetes cluster to have more nodes, the issue did not come up anymore.
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#24429): https://lists.onap.org/g/onap-discuss/message/24429 Mute This Topic: https://lists.onap.org/mt/95061105/21656 Mute #oom:https://lists.onap.org/g/onap-discuss/mutehashtag/oom Mute #strimzi:https://lists.onap.org/g/onap-discuss/mutehashtag/strimzi Mute #error:https://lists.onap.org/g/onap-discuss/mutehashtag/error Mute #retry:https://lists.onap.org/g/onap-discuss/mutehashtag/retry Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
