breaking: remove servieaccount auth mode - #175
Conversation
|
Warning Review limit reached
Next review available in: 51 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. 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: Repository YAML (base), Organization UI (inherited) Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (9)
📝 WalkthroughWalkthroughThe supported authentication modes now consist of Estimated code review effort: 3 (Moderate) | ~20 minutes Suggested reviewers: 🚥 Pre-merge checks | ✅ 4✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
d76684e to
7a4e1be
Compare
| @@ -85,7 +85,7 @@ go run ./cmd/obs-mcp/ --listen 127.0.0.1:9100 --auth-mode kubeconfig --metrics-b | |||
| > 2. `LOKI_URL` environment variable | |||
| > 3. Default: `http://localhost:3100` (kubeconfig mode only) | |||
There was a problem hiding this comment.
needs to be updated as well. It seems the logic is simpler now: it's wither the --loki-url/LOKI_URL or discovery, regardless of the auth method, right?
| > 3. Default: `http://localhost:3100` (kubeconfig mode only) | ||
| > | ||
| > In `header` and `serviceaccount` modes, you can either set `--loki-url`/`LOKI_URL` **or** use LokiStack discovery (`loki_list_instances` + `lokiNamespace`/`lokiName` arguments). | ||
| > In `header` mode, you can either set `--loki-url`/`LOKI_URL` **or** use LokiStack discovery (`loki_list_instances` + `lokiNamespace`/`lokiName` arguments). |
There was a problem hiding this comment.
This would now work in all modes it seems? I approved #177, let's wait for that and rebase with resolved conflicts.
There was a problem hiding this comment.
You're right. I reworked the entire box now, and also added one for Tempo.
The kubeconfig auth mode already reads the mounted service account token in case kubeconfig is not found. Signed-off-by: Andreas Gerstmayr <agerstmayr@redhat.com>
7a4e1be to
1434c8d
Compare
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: andreasgerstmayr, iNecas The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
The
kubeconfigauth mode already reads the mounted service account token in case kubeconfig is not found.