chore: bump Bifrost Helm chart to 2.1.19 with bug fixes and changelog reorganization - #3755
Merged
Merged
Conversation
Contributor
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
📝 WalkthroughSummary by CodeRabbitRelease Notes
WalkthroughBifrost Helm chart version bumped from 2.1.18 to 2.1.19. Chart.yaml declares the new version, README.md reorganizes changelog entries to mark 2.1.19 as latest while refactoring prior release notes, and index.yaml adds the new chart release entry with updated timestamps. ChangesBifrost Helm Chart Release 2.1.19
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~5 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Contributor
Author
This stack of pull requests is managed by Graphite. Learn more about stacking. |
BearTS
changed the title
BearTS
marked this pull request as ready for review
May 26, 2026 09:04
Contributor
Confidence Score: 5/5Safe to merge — all three changed files are packaging and documentation artifacts with no runtime logic. The diff touches only Chart.yaml (version string), README.md (changelog text), and index.yaml (Helm repo index entry). None of these files contain executable template logic; the actual bug-fix and feature templates were committed to dev separately. The changelog reorganisation and version numbers are internally consistent. No files require special attention. Important Files Changed
Reviews (2): Last reviewed commit: "Update README.md" | Re-trigger Greptile |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
akshaydeo
approved these changes
May 26, 2026
Contributor
Merge activity
|
akshaydeo
pushed a commit
that referenced
this pull request
May 26, 2026
… reorganization (#3755) Releases Bifrost Helm chart version 2.1.19, incorporating several bug fixes and new configuration options introduced since 2.1.18. - Bumped chart version from `2.1.18` to `2.1.19` - Added `existingSecret` support for hosted PostgreSQL, allowing `postgresql.auth.existingSecret` and `postgresql.auth.passwordKey` to reference a Kubernetes secret instead of a plaintext password - Added `postgresql.primary.podSecurityContext` and `postgresql.primary.containerSecurityContext` to support clusters enforcing strict Kyverno/OPA security policies - Added `bifrost.featureFlags` map to `values.yaml` and `_helpers.tpl`, rendering into `feature_flags.flags` in the generated config JSON - Fixed Deployment not exposing the cluster gRPC container port and `service.yaml` missing the gRPC service port - Fixed Weaviate PVC rendering when `vectorStore.weaviate.persistence.enabled=false` - Fixed Redis probes passing password via `-a` flag; switched to `REDISCLI_AUTH` env var - Fixed nondeterministic env var ordering for `providerSecrets` and `weaviate.env` map iterations by sorting keys with `sortAlpha` - Corrected guardrail `timeout` example values in `values.yaml` - Moved `bifrost.framework.pricing.modelParametersUrl` (previously `bifrost.modelCatalog.modelParametersUrl`) into the 2.1.18 changelog entry where it was originally introduced - [x] Bug fix - [x] Feature - [ ] Refactor - [ ] Documentation - [ ] Chore/CI - [ ] Core (Go) - [ ] Transports (HTTP) - [ ] Providers/Integrations - [ ] Plugins - [ ] UI (React) - [ ] Docs ```sh helm repo update helm install bifrost bifrost/bifrost --version 2.1.19 --dry-run ``` To validate `existingSecret` support: ```sh helm install bifrost bifrost/bifrost \ --set postgresql.enabled=true \ --set postgresql.auth.existingSecret=my-pg-secret \ --set postgresql.auth.passwordKey=password \ --dry-run ``` - [ ] Yes - [x] No The `existingSecret` support for PostgreSQL allows operators to avoid storing plaintext passwords in Helm values, enabling integration with secret management tools such as the Vault Secrets Operator. The chart-managed secret is not created when `existingSecret` is set. - [ ] I read `docs/contributing/README.md` and followed the guidelines - [ ] I added/updated tests where appropriate - [ ] I updated documentation where needed - [ ] I verified builds succeed (Go and UI) - [ ] I verified the CI pipeline passes locally if applicablecs
This was referenced May 28, 2026
This was referenced Jun 8, 2026
This was referenced Jul 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Releases Bifrost Helm chart version 2.1.19, incorporating several bug fixes and new configuration options introduced since 2.1.18.
Changes
2.1.18to2.1.19existingSecretsupport for hosted PostgreSQL, allowingpostgresql.auth.existingSecretandpostgresql.auth.passwordKeyto reference a Kubernetes secret instead of a plaintext passwordpostgresql.primary.podSecurityContextandpostgresql.primary.containerSecurityContextto support clusters enforcing strict Kyverno/OPA security policiesbifrost.featureFlagsmap tovalues.yamland_helpers.tpl, rendering intofeature_flags.flagsin the generated config JSONservice.yamlmissing the gRPC service portvectorStore.weaviate.persistence.enabled=false-aflag; switched toREDISCLI_AUTHenv varproviderSecretsandweaviate.envmap iterations by sorting keys withsortAlphatimeoutexample values invalues.yamlbifrost.framework.pricing.modelParametersUrl(previouslybifrost.modelCatalog.modelParametersUrl) into the 2.1.18 changelog entry where it was originally introducedType of change
Affected areas
How to test
To validate
existingSecretsupport:Breaking changes
Related issues
Security considerations
The
existingSecretsupport for PostgreSQL allows operators to avoid storing plaintext passwords in Helm values, enabling integration with secret management tools such as the Vault Secrets Operator. The chart-managed secret is not created whenexistingSecretis set.Checklist
docs/contributing/README.mdand followed the guidelines