Challenge

NGINX Ingress Controller manages external access to your Kubernetes services — but subtle misconfigurations or edge-case failures can silently cause outages, routing errors, or degraded performance across your applications.

Your task:
Reproduce a high-severity failure involving the NGINX Ingress Controller on a recent release and write a detection rule that reliably flags this issue in real-world production environments.

Prizes

🏆 Technical Champion - Awarded to the highest quality PR

• All on-time PRs will be reviewed for
  • difficulty
  • quality
  • completeness
• The winning PR will be merged, you will receive the full bounty, and get featured on the Prequel blog.

⭐ Community Champion - Awarded to the submission most loved by the community

• To participate in this category, you must
  • Share your PR online (X or other forums)
    • tag: @prequel-dev and @kubernetesio
    • describe the problem you are detecting
  • Embed a link to your social posts in your PR comment
  • Follow prequel on X @prequel_dev and LinkedIn [prequel-dev] (https://www.linkedin.com/company/prequel-dev/)
• Your PR will be merged and you will receive a $50 bounty.

🙌 All other merged PRs will receive a $20 bounty. (Max 10)

✅ You must:

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

📦 Deliverables:

• Reproduction setup and clear README
  • create a private repo and invite the maintainers (@tonymeehan @Lyndon-prequel)
• Link to your unique rule in the CRE playground
• PR containing
  • the new CRE rule
  • example logs in test.log
  • updated tags.yaml and category.yaml files
• Short demo video of
  • your reproduction
  • running the rule. i.e cat test.log | preq -r your_rule.yaml -d

💰 /bounty $200