Skip to content

fix(helm): remediate igloo-pg apps by uninstall instead of rollback #1838

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
slipperypenguin wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

fix(helm): remediate igloo-pg apps by uninstall instead of rollback #1838

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions kubernetes/apps/default/litellm/app/helmrelease.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,14 @@ spec:
timeout: 20m
upgrade:
cleanupOnFail: true
timeout: 20m
remediation:
# With DISABLE_SCHEMA_UPDATE "False", litellm applies forward-only Prisma
# migrations to igloo-pg on startup. Rolling back to an older image after
# a migration lands risks running it against a schema it doesn't know, so
# remediate by uninstalling and reinstalling the desired version. All
# state lives in Postgres, so an uninstall removes nothing persistent.
strategy: uninstall
retries: 3
values:
controllers:
Expand Down
7 changes: 7 additions & 0 deletions kubernetes/apps/default/open-webui/app/helmrelease.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,14 @@ spec:
retries: -1
upgrade:
cleanupOnFail: true
timeout: 15m
remediation:
# open-webui runs forward-only alembic migrations against igloo-pg on
# startup. Once one lands, rolling back can never succeed (the older image
# can't locate the newer revision), so remediate by uninstalling and
# reinstalling the desired version. The data PVC is an existingClaim and
# chat data lives in Postgres, so neither is removed by an uninstall.
strategy: uninstall
retries: 3
values:
controllers:
Expand Down
Loading