You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Repoint nan-system-dev platform-api at litellm-test and rotate the prod LiteLLM master key #127
Onboarding a user in dev therefore mints prod LiteLLM keys and writes the prod LiteLLM DB.
helmcode/nan-devops#650 (ingress NetworkPolicies for the LiteLLM namespaces, GHSA-4xpc) deliberately does not allow nan-system-dev on the prod :4000 and :5432 policies. It is allowed only on litellm-test. Once #650 is rolled out, dev loses prod LiteLLM access. That is intended.
Tasks
Repoint dev at litellm-test. In Vault, for nan-system-dev/platform-api-secrets:
litellm-master-key -> the litellm-test master key;
litellm-db-url -> litellm-test-pg-rw.litellm-test.svc.cluster.local:5432, with a litellm-test role;
the litellm-team-* / litellm-premium-team-id values -> teams that exist in litellm-test.
Then let VSO sync, and restart dev platform-api.
Rotate the prod community master key, since dev has held it:
update nan-system/platform-api-secrets and every other consumer of the prod master key;
verify that platform-api key lifecycle, the discord bot's metrics job (nan-eu001, which holds LITELLM_ADMIN_KEY) and gatus keep working;
confirm that the old key returns 401.
Verify dev's LiteLLM features against litellm-test: onboarding (key creation in the right team), key revoke, usage and spend reads, model listing, and any feature that reads the LiteLLM DB.
Check that no dev-created keys are left in prod LiteLLM. Keys created by dev onboarding carry dev members' user ids or aliases: list them and decide whether to delete.
Activity