The Problem 

Currently, it is difficult to debug kata issues without enabling specific debug options and using the existing tools like crictl, podman, rust agent debug console, shimv2 debug output, crio log_level=debug etc. However, some of those facilities are either broken right now or could be broken in the future, and we don’t have any assurance at the moment.

The general logging and must-gather would not help much in this situation because those specific debugging facilities are only enabled on demand by developers and triage engineers for specific scenarios.

Existing tools

• must-gather 
• Sosreport
• Insights Operator

Requirements 

Make sure all those debugging facilities are always working properly both upstream and downstream. Probably create an official downstream kata container debugging guide for support organizations to consume.

References

https://docs.google.com/document/d/14M250jxwCjkggbdYwPudYZHBiiv6HrBU2S52YHNtmtI/edit#