Setup automated service mesh configuration

[BigBen-7]

Description

Auto-configure service mesh.

Requirements

• Automatic sidecar injection
• Traffic routing rules
• Circuit breaker config
• Retry policies
• Timeout configuration

Files to Touch

• infrastructure/scripts/configure-mesh.sh
• infrastructure/k8s/mesh-config/
• infrastructure/docs/service-mesh.md

Complexity: 350 points

[devbackend513-ux]

@devbackend513-ux has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

i would like to take this

ℹ️ Repo Maintainers: To accept this application, review their application or assign @devbackend513-ux to this issue.

[testersweb0-bug]

@testersweb0-bug has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

I’d like to take this issue.

This is an infrastructure automation task focused on standardizing service mesh behavior across the cluster, ensuring consistent traffic control, resilience, and observability without manual per-service configuration.

I’ll implement an automated setup script in infrastructure/scripts/configure-mesh.sh that enables sidecar injection by default and applies baseline mesh policies across namespaces. I’ll also define the core mesh configuration under infrastructure/k8s/mesh-config/, including traffic routing rules, retry policies, circuit breaker settings, and timeout constraints to ensure stable service-to-service communication under load.

Finally, I’ll document the full setup and operational behavior in infrastructure/docs/service-mesh.md, including how injection is enabled, how policies are applied, and how to extend configurations for new services.

The goal is a repeatable, production-ready mesh bootstrap that enforces reliability patterns consistently across the system.

ETA: 3–4 hours.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @testersweb0-bug to this issue.

[OlaBakare]

@OlaBakare has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

Hi, I'd like to work on this issue.
I can handle it.
Thank you.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @OlaBakare to this issue.

[drips-wave]

Congratulations, @devbackend513-ux! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 2, 2026.

🧑‍💻 @devbackend513-ux: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[drips-wave]

This issue has been completed by @devbackend513-ux as part of the Stellar Wave Program's 5th Wave 🥳

😎 @devbackend513-ux: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.