At the moment, the indexer's pod is not restarted if the container exists with a 0 exit code.
In production this causes some issues because while in theory no indexer exits with exit code 0 , in practice it happens and the indexer is not restarted.
To Reproduce
This is hard to reproduce, probably the easiest way is by setting the ENDING_BLOCK environment variable to stop the indexer when it reaches that block.
Expected behavior
The indexer pod should be restarted and the restart count should be incremented.
Describe the bug
At the moment, the indexer's pod is not restarted if the container exists with a
0exit code. In production this causes some issues because while in theory no indexer exits with exit code0, in practice it happens and the indexer is not restarted.To Reproduce
This is hard to reproduce, probably the easiest way is by setting the
ENDING_BLOCKenvironment variable to stop the indexer when it reaches that block.Expected behavior
The indexer pod should be restarted and the restart count should be incremented.
Additional context
Probably need an extra check in this code