fix: follow the redirect the detector's ingress answers with - #14
Conversation
The detector's ingress sets allowInsecure false, so a plain HTTP request is answered with a redirect to HTTPS rather than being served. The readiness probe used a client that does not follow redirects, so every attempt saw a non-200 and reported the endpoint as not serving. A redirect from the proxy does not start an app scaled to zero either, so the detector was never activated and the wait could only ever expire. The same URL worked from the guardrail because the OpenAI client follows redirects by default. The two clients disagreeing is what made this look like a networking problem rather than a client one. The probe now records the status it received. "Not ready" covers a redirect, a rejection and a service still starting, and telling them apart from the logs is what identified this.
|
Warning Review limit reached
Next review available in: 25 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the 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 configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
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. Comment |
1 participant
The detector's ingress sets allowInsecure false, so a plain HTTP request is answered with a redirect to HTTPS rather than being served. The readiness probe used a client that does not follow redirects, so every attempt saw a non-200 and reported the endpoint as not serving. A redirect from the proxy does not start an app scaled to zero either, so the detector was never activated and the wait could only ever expire.
The same URL worked from the guardrail because the OpenAI client follows redirects by default. The two clients disagreeing is what made this look like a networking problem rather than a client one.
The probe now records the status it received. "Not ready" covers a redirect, a rejection and a service still starting, and telling them apart from the logs is what identified this.