Turn a manual troubleshooting guide into a library of CREs

We have a technical guide that walks through a specific set of reliability issues. Your task is to reproduce issues and break them down into a structured set of CREs that can be shared with the community and used by preq to automate problem detection.

This a great opportunity to get hands-on experience with popular technologies.

📌 What you’ll do

• Read the guide
• Reproduce 10 issues
• Extract and document multiple CREs based on the key failure modes, signals, and remediations described.
• Submit them in the Prequel CRE format following the structure of this repo.

✅ What we’re looking for

• At least 10 high-quality CREs

🏆 Award

$300 if the submission hits all criteria

⚙️ Process

• We'll leave this bounty unassigned for 3 days. We encourage anyone interested to comment /attempt Istio Ambient Troubleshooting Rules #81 on the issue
• We will then assign the bounty to a someone based on
  • quality of plan
  • past contributions
    ** The assignee will have 5 days to exclusively pursue the bounty. If the work is not completed, the bounty may be reassigned **

✅ You must:

1. Reproduce the failure scenarios
2. Share a minimal, working reproductions (e.g., Helm, Docker Compose, etc.)
3. Write unique CRE-format detection rules for preq
4. Install preq and run the rules

📦 Deliverables:

• Reproduction setup and clear README
  • create a private repo and invite the maintainers (@tonymeehan @Lyndon-prequel)
• Link to your rules in seperate CRE playgrounds
• PR containing
  • the new CRE rules
  • example logs in test.log files
  • updated tags.yaml and category.yaml files
  • updated data-sources.yaml file
• Demo video of
  • your reproductions
  • running the rules

📅 Deadline

Will be assigned by Aug 29
Submit your pull request by Submit by September 3 11:59 pm ET

Questions? Open a discussion or find us on slack. Happy hunting!

/bounty 300