chore: release Bifrost Helm chart v2.1.37 with Splunk HEC plugin, OTel/logging semaphore controls, PostgreSQL node scheduling, and separate logs-store Postgres - #6542
Merged
Conversation
Contributor
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (4)
Included review availability: 4 reviews are currently available. Your included PR review attempts over the past 7 days set your current allowance at 5 reviews per hour. 📝 WalkthroughSummary by CodeRabbit
WalkthroughThe PR publishes Helm chart version 2.1.37 and adds its release notes to the chart README, documentation changelog, and documentation navigation. ChangesHelm release
Estimated code review effort: 1 (Trivial) | ~5 minutes Merge Risk: ⚪ Minimal · up to This release updates chart metadata and documentation for the stated Helm chart changes; no actionable merge-blocking risk remains beyond normal checks and review. Suggested reviewers: 🚥 Pre-merge checks | ✅ 3 | ❌ 2❌ Failed checks (2 warnings)
✅ Passed checks (3 passed)
Full details: Linked Issues checkExplanation The changeset releases Helm chart v2.1.37 and adds Splunk, injection, PostgreSQL scheduling, and logs-store configuration features. It does not implement the directly linked Files API support requested by issue Resolution Implement the Files API requirements from issue Full details: Docstring CoverageExplanation No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (4 skipped: 4 unsupported.) Full details: Description checkExplanation The description provides a clear summary, detailed changes, testing steps, and rationale. It omits several template sections, including type, affected areas, breaking changes, related issues, security considerations, and checklist items, but the core release information is complete.
✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
🧪 Generate unit tests (beta)
Comment |
Contributor
Author
This stack of pull requests is managed by Graphite. Learn more about stacking. |
BearTS
marked this pull request as ready for review
August 26, 2026 08:34
BearTS
changed the title
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
Merge activity
|
akhsaul
pushed a commit
to akhsaul/bifrost
that referenced
this pull request
Aug 27, 2026
…l/logging semaphore controls, PostgreSQL node scheduling, and separate logs-store Postgres (maximhq#6542) ### TL;DR Releases Bifrost Helm chart v2.1.37 with Splunk HEC support, OTel/logging concurrency controls, PostgreSQL node scheduling options, and a separate logs store PostgreSQL configuration. ### What changed? - Added `bifrost.plugins.splunk` to enable the Splunk HTTP Event Collector (HEC) observability connector (Enterprise). Supports sending one flattened event per request to `events_index` and derived metrics to `metrics_index`, with TLS options (`ca_cert` / `insecure_skip_verify`), content logging toggle (`disable_content_logging`), request-header capture, and indexer acknowledgement controls (`indexer_ack`, `ack_poll_interval_ms`, `ack_timeout_ms`, `max_ack_attempts`). - Added `semaphore_size` and `inject_timeout` to `bifrost.plugins.otel.config` (defaulting to `10000` and `5` respectively) to cap concurrent in-flight trace injects and prevent a hung collector from holding a concurrency slot indefinitely. The same keys are also accepted under `bifrost.plugins.logging.config`, with `inject_timeout` expressed as a duration string (e.g. `"5s"`). - Added `postgresql.primary.nodeSelector`, `postgresql.primary.tolerations`, and `postgresql.primary.affinity` to allow the hosted PostgreSQL deployment to be scheduled independently of the Bifrost pod. All three default to empty, preserving existing rendering behavior unless explicitly set. - Added `storage.logsStore.postgres` to configure a separate external PostgreSQL instance for the logs store, distinct from the config store. Disabled by default (`enabled: false`), preserving existing behavior. Supports the same fields as `postgresql.external`, and when `existingSecret` is used, the password is injected via the `BIFROST_LOGS_POSTGRES_PASSWORD` environment variable. ### How to test? - Deploy the chart at v2.1.37 and configure `bifrost.plugins.splunk` with a valid Splunk HEC endpoint, then verify events and metrics appear in the configured indexes. - Set `semaphore_size` and `inject_timeout` under `bifrost.plugins.otel.config` and confirm trace injection respects the concurrency cap and timeout under load. - Apply `postgresql.primary.nodeSelector` or `tolerations` and verify the hosted PostgreSQL pod is scheduled to the intended nodes. - Enable `storage.logsStore.postgres` pointing to a separate PostgreSQL instance and confirm logs are written to that database while the config store remains unaffected. ### Why make this change? These additions expand observability options with Splunk HEC support, improve resilience of trace injection under collector failures, provide finer control over PostgreSQL pod placement for scaling scenarios, and allow the logs store to be separated from the config store for independent scaling and management.
occcat
pushed a commit
to occcat/bifrost
that referenced
this pull request
Sep 2, 2026
…l/logging semaphore controls, PostgreSQL node scheduling, and separate logs-store Postgres (maximhq#6542) ### TL;DR Releases Bifrost Helm chart v2.1.37 with Splunk HEC support, OTel/logging concurrency controls, PostgreSQL node scheduling options, and a separate logs store PostgreSQL configuration. ### What changed? - Added `bifrost.plugins.splunk` to enable the Splunk HTTP Event Collector (HEC) observability connector (Enterprise). Supports sending one flattened event per request to `events_index` and derived metrics to `metrics_index`, with TLS options (`ca_cert` / `insecure_skip_verify`), content logging toggle (`disable_content_logging`), request-header capture, and indexer acknowledgement controls (`indexer_ack`, `ack_poll_interval_ms`, `ack_timeout_ms`, `max_ack_attempts`). - Added `semaphore_size` and `inject_timeout` to `bifrost.plugins.otel.config` (defaulting to `10000` and `5` respectively) to cap concurrent in-flight trace injects and prevent a hung collector from holding a concurrency slot indefinitely. The same keys are also accepted under `bifrost.plugins.logging.config`, with `inject_timeout` expressed as a duration string (e.g. `"5s"`). - Added `postgresql.primary.nodeSelector`, `postgresql.primary.tolerations`, and `postgresql.primary.affinity` to allow the hosted PostgreSQL deployment to be scheduled independently of the Bifrost pod. All three default to empty, preserving existing rendering behavior unless explicitly set. - Added `storage.logsStore.postgres` to configure a separate external PostgreSQL instance for the logs store, distinct from the config store. Disabled by default (`enabled: false`), preserving existing behavior. Supports the same fields as `postgresql.external`, and when `existingSecret` is used, the password is injected via the `BIFROST_LOGS_POSTGRES_PASSWORD` environment variable. ### How to test? - Deploy the chart at v2.1.37 and configure `bifrost.plugins.splunk` with a valid Splunk HEC endpoint, then verify events and metrics appear in the configured indexes. - Set `semaphore_size` and `inject_timeout` under `bifrost.plugins.otel.config` and confirm trace injection respects the concurrency cap and timeout under load. - Apply `postgresql.primary.nodeSelector` or `tolerations` and verify the hosted PostgreSQL pod is scheduled to the intended nodes. - Enable `storage.logsStore.postgres` pointing to a separate PostgreSQL instance and confirm logs are written to that database while the config store remains unaffected. ### Why make this change? These additions expand observability options with Splunk HEC support, improve resilience of trace injection under collector failures, provide finer control over PostgreSQL pod placement for scaling scenarios, and allow the logs store to be separated from the config store for independent scaling and management.
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.
TL;DR
Releases Bifrost Helm chart v2.1.37 with Splunk HEC support, OTel/logging concurrency controls, PostgreSQL node scheduling options, and a separate logs store PostgreSQL configuration.
What changed?
bifrost.plugins.splunkto enable the Splunk HTTP Event Collector (HEC) observability connector (Enterprise). Supports sending one flattened event per request toevents_indexand derived metrics tometrics_index, with TLS options (ca_cert/insecure_skip_verify), content logging toggle (disable_content_logging), request-header capture, and indexer acknowledgement controls (indexer_ack,ack_poll_interval_ms,ack_timeout_ms,max_ack_attempts).semaphore_sizeandinject_timeouttobifrost.plugins.otel.config(defaulting to10000and5respectively) to cap concurrent in-flight trace injects and prevent a hung collector from holding a concurrency slot indefinitely. The same keys are also accepted underbifrost.plugins.logging.config, withinject_timeoutexpressed as a duration string (e.g."5s").postgresql.primary.nodeSelector,postgresql.primary.tolerations, andpostgresql.primary.affinityto allow the hosted PostgreSQL deployment to be scheduled independently of the Bifrost pod. All three default to empty, preserving existing rendering behavior unless explicitly set.storage.logsStore.postgresto configure a separate external PostgreSQL instance for the logs store, distinct from the config store. Disabled by default (enabled: false), preserving existing behavior. Supports the same fields aspostgresql.external, and whenexistingSecretis used, the password is injected via theBIFROST_LOGS_POSTGRES_PASSWORDenvironment variable.How to test?
bifrost.plugins.splunkwith a valid Splunk HEC endpoint, then verify events and metrics appear in the configured indexes.semaphore_sizeandinject_timeoutunderbifrost.plugins.otel.configand confirm trace injection respects the concurrency cap and timeout under load.postgresql.primary.nodeSelectorortolerationsand verify the hosted PostgreSQL pod is scheduled to the intended nodes.storage.logsStore.postgrespointing to a separate PostgreSQL instance and confirm logs are written to that database while the config store remains unaffected.Why make this change?
These additions expand observability options with Splunk HEC support, improve resilience of trace injection under collector failures, provide finer control over PostgreSQL pod placement for scaling scenarios, and allow the logs store to be separated from the config store for independent scaling and management.