Skip to content

Add first-class WAL footer version and auto-derived storage URIs#76

Open
Alex Soldatchenko (soldatchenko) wants to merge 10 commits intomainfrom
feature/first-class-upgrade-vars
Open

Add first-class WAL footer version and auto-derived storage URIs#76
Alex Soldatchenko (soldatchenko) wants to merge 10 commits intomainfrom
feature/first-class-upgrade-vars

Conversation

@soldatchenko
Copy link
Copy Markdown

@soldatchenko Alex Soldatchenko (soldatchenko) commented Apr 10, 2026

Adds chart support for the Data Plane 2.0 upgrade path. brainstoreWalFooterVersion is now a first-class value, BRAINSTORE_RESPONSE_CACHE_URI and BRAINSTORE_CODE_BUNDLE_URI are auto-derived from existing objectStorage config on all Brainstore pods, and WAL_USE_EFFICIENT_FORMAT is decoupled to fire on either WAL footer version or skipPg.

  • brainstoreWalFooterVersion sets BRAINSTORE_WAL_FOOTER_VERSION on API pod
  • WAL_USE_EFFICIENT_FORMAT fires when either brainstoreWalFooterVersion or skipPgForBrainstoreObjects is set
  • RESPONSE_CACHE_URI / CODE_BUNDLE_URI auto-derived from objectStorage config (AWS, GCP, Azure) on reader/writer/fastreader
  • Added AGENTS.md with upgrade safety constraints

@soldatchenko Alex Soldatchenko (soldatchenko) changed the title DRAFT: Add first-class WAL footer version, decoupled efficient format, and auto-derived storage URIs Add first-class WAL footer version and auto-derived storage URIs Apr 10, 2026
@soldatchenko Alex Soldatchenko (soldatchenko) marked this pull request as ready for review April 10, 2026 23:28
@mdeeks
Copy link
Copy Markdown
Contributor

Can you change this PR description to tell users context and what, if anything, they need to do?

I don't think any customer reading this will understand

BRAINSTORE_LOCKS_URI: "az://{{ .Values.objectStorage.azure.brainstoreContainer }}/brainstore/locks"
{{- end }}
{{- if .Values.objectStorage.azure.responseContainer }}
BRAINSTORE_RESPONSE_CACHE_URI: "az://{{ .Values.objectStorage.azure.responseContainer }}"
Copy link
Copy Markdown
Contributor

@mdeeks Mike Deeks (mdeeks) Apr 11, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I dont think this is right? There should be a path I think? Can you please double and triple check all of these? If we get them wrong it is essentially impossible to fix later.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants