Skip to content

docs: verify old gateway compatibility before rolling upgrades - #3036

Open
anencore94 wants to merge 1 commit into
BerriAI:mainfrom
anencore94:docs/verify-rolling-upgrade
Open

anencore94 wants to merge 1 commit into
BerriAI:mainfrom
anencore94:docs/verify-rolling-upgrade

Conversation

@anencore94

@anencore94 anencore94 commented Nov 15, 2026 •

Copy link
Copy Markdown

Operators can now check whether old gateway pods continue serving against the upgraded schema. The guide explains how to keep old database sessions active during rehearsal, replay representative requests after the target migration, and schedule a maintenance window if the old version fails.

This addresses the operator guidance in BerriAI/litellm#41743. The guide links the virtual-key cached-plan incident in BerriAI/litellm#36418.

Validation passed for writing, document structure, model examples (20 tests), and search (118 tests). The local production build also passed and generated the static site.

@vercel

vercel Bot commented Nov 15, 2026

Copy link
Copy Markdown

@anencore94 is attempting to deploy a commit to the Berri AI Team on Vercel.

A member of the Team first needs to authorize it.

@anencore94
anencore94 marked this pull request as ready for review November 15, 2026 11:59

anencore94 commented Nov 15, 2026 •

Copy link
Copy Markdown
Author

@ryan-crabbe-berri thanks for pointing me to the upgrade guide and talking through the migration job.
I've updated the docs as what we discussed in the call and linkedin.
Could you review the new pre-upgrade check? It shows operators how to rehearse the target migration with old gateway sessions still open and when to schedule downtime if the old version fails.

This branch has not been deployed

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant