feat: expose gateway via team-setops.stud.k8s.aet.cit.tum.de

[memreo]

Summary

Advisor asked for the deployment to be reachable under our TUM subdomain instead of the raw LoadBalancer IP. Added an Ingress routing team-setops.stud.k8s.aet.cit.tum.de to the gateway service, using the cluster's letsencrypt-prod ClusterIssuer for TLS (same pattern as the w04-template reference chart).

Component

• Client: client/
• API contract: api/
• Spring ingestion: services/spring-ingestion/
• Spring logbook: services/spring-logbook/
• Spring alerts: services/spring-alerts/
• GenAI: services/py-intelligence/
• Infrastructure: infra/
• CI/CD: .github/workflows/
• Documentation

API Impact

• This does not change the API.

Testing

• I tested this locally.

Applied to the cluster and confirmed the domain resolves with a valid cert.

Checklist

• Branch name follows (feat|fix)/(issue_id)/(name_of_issue) — no issue for this one, used a descriptive name.
• The change is limited to the intended component(s).
• Documentation was updated if needed.

Related Issue

No related issue.

[coderabbitai]

Warning

Review limit reached

@memreo, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 58 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 242eaf46-fdbf-44a4-bae0-57525b0a56ba

📥 Commits

Reviewing files that changed from the base of the PR and between 7d3abfb and b7b14b5.

📒 Files selected for processing (4)

• README.md
• client/vite.config.js
• infra/k8s/ingress.yaml
• infra/k8s/kustomization.yaml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/ingress-team-domain

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[sachmii]

Looks good, thank you