One of the ways that TRT identifies problematic jobs and tests is by using the Sippy tool. What Sippy does is ingest aggregate test data from TestGrid and computes statistics over time while also being able to refer a specific job run or test failure.

Currently, Sippy uses a config file to determine which jobs it should watch. This file is generated by a config generator which is hard-coded to ignore OKD jobs. At the very least, we'll need to update the config generator so that it does not ignore OKD jobs and use the updated config generator to regenerate the Sippy config.

This will likely involve some coordination / consulting with the TRT team to better understand how best to add this configuration.

Done When:

• Sippy is ingesting and reporting on OKD job failures.