chore: bump Bifrost Helm chart to 2.1.18 with feature flags, model catalog URL, and bug fixes#3623
Conversation
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
📝 WalkthroughWalkthroughBifrost Helm chart version is bumped to 2.1.18 with updates to the chart manifest version field, README changelog documentation describing release fixes and feature additions, and Helm repository index refresh with new package metadata and timestamp. ChangesHelm Chart Release 2.1.18
Estimated Code Review Effort🎯 1 (Trivial) | ⏱️ ~3 minutes Suggested Reviewers
Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
Warning This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
This stack of pull requests is managed by Graphite. Learn more about stacking. |
Confidence Score: 5/5Safe to merge — changes are limited to the chart version bump, a README changelog entry, and a new Helm index entry that uses the same hosting domain as all prior releases. All three changed files are metadata or documentation. The index entry for 2.1.18 is self-consistent with the rest of the index (same URL pattern, matching appVersion, valid SHA-256 digest field). No files require special attention. Important Files Changed
Reviews (5): Last reviewed commit: "chore: helm chart version bump" | Re-trigger Greptile |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@helm-charts/index.yaml`:
- Line 26: The new chart URL entry
'https://helm.getbifrost.ai/bifrost-2.1.18.tgz' is currently unreachable
(DNS/curl failure); revert or replace it with the previously working host URL
(e.g., the prior maximhq.github.io chart URL) in the index entry or remove the
new host line until helm.getbifrost.ai is DNS-resolvable and the artifact is
fetchable, then re-add and verify accessibility before merging.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: b80bb906-9e92-4916-b507-a57e088547e7
📒 Files selected for processing (3)
helm-charts/bifrost/Chart.yamlhelm-charts/bifrost/README.mdhelm-charts/index.yaml
9b9fc62 to
164b903
Compare
15a056a to
a3b93b2
Compare
164b903 to
7a46efe
Compare
a3b93b2 to
b6bdaad
Compare
7a46efe to
8fef3f3
Compare
b6bdaad to
355cc41
Compare

Summary
Bumps the Bifrost Helm chart to version
2.1.18, introducing new configuration options, fixing several rendering and runtime bugs, and updating the Helm index accordingly.Changes
bifrost.featureFlagsmap tovalues.yamland_helpers.tpl, rendering intofeature_flags.flagsin the generated config JSON. Each entry accepts a literal boolean or"env.NAME"string.bifrost.modelCatalog.modelParametersUrlto allow operators to override the URL Bifrost uses to fetch model parameter definitions.service.yamlmissing the gRPC service port, aligning both with StatefulSet/headless service behaviour.vectorStore.weaviate.persistence.enabled=false; PVC is now gated on persistence being enabled.-aflag in process args; switched to theREDISCLI_AUTHenvironment variable to avoid credential exposure.providerSecretsandweaviate.envmap iterations by sorting keys withsortAlpha.timeoutexample values invalues.yaml(provider default30s, rule default60s).access_profile_idto the virtual key block in_helpers.tpl, enabling virtual keys to be assigned to an access profile.Type of change
Affected areas
How to test
Breaking changes
Related issues
N/A
Security considerations
The Redis probe fix removes the password from process arguments, preventing credential leakage via
/procor process listings. No other security-sensitive changes.Checklist
docs/contributing/README.mdand followed the guidelines