On debugging, looks like the config node is unaware of this pod at that moment. So no entry is trickled to control node and the agent. It could be a case of either rabbitMq notification or config node processing after the config api reset
On debugging, looks like the config node is unaware of this pod at that moment. So no entry is trickled to control node and the agent. It could be a case of either rabbitMq notification or config node processing after the config api reset