It would be really cool if this included some wheels of misfortune down the line. Would be nice to help get people acclimated to debugging some more common issues like unmet PVCs, node with bad disk/hardware, pods with incorrect resource limit & claim, etc.

Hello @gravypod I'm one of the maintainer of this page. Thanks for your feedback. We do have plans to include troubleshooting guide in near future. Luckily, it's contribution coming from the community, hence you can contribute too for this.

Understanding Day 2 & Day 3 of Operators can be quite daunting. It would be nice to practice with failure, eg loosing a PVC, and then assist the Operator back to normal operations.

What Operator could be used for that? Good enough to handle some failure scenarios by itself and with good metrics to allow alerting for scenarios that need manual intervention. Simple enough to use in an exercise. And managing a Statefull Application, as imho that is what the most important Operators in a kubernetes cluster will manage.

Links broken or down and .HTML should be .MD .

Thanks for your feedback. We are continously working on the links and getting it fixed. It's completely community work and we working together to make it useful for the community.

need to change the .html links in the main page into .md ones

I will update today @lazyant thanks