Skip to content

docs: document Bitovi platform deployment in README#7

Open
DavidNic11 wants to merge 1 commit into
litellm_internal_stagingfrom
docs/platform-deployment
Open

docs: document Bitovi platform deployment in README#7
DavidNic11 wants to merge 1 commit into
litellm_internal_stagingfrom
docs/platform-deployment

Conversation

@DavidNic11

Copy link
Copy Markdown

Adds a "Bitovi Fork — Platform Deployment" section to the top of the README (above the upstream LiteLLM content, clearly marked as fork-specific), documenting how claude-usage-proxy is deployed and operated on the platform.

Covers the three change paths people actually need:

To change… Where
LiteLLM version / fork code tag vX.Y.Z off litellm_internal_staging
Model routing / proxy config PR to bitovi/claude-usage-proxy (deploy/manifests/litellm_config.yaml)
Infra shape (ingress, Postgres, autoscaling, Bedrock, env) deploy/values.yaml here + staging → platform-deploy merge

Plus key facts: the platform-deploy branch role, OIDC/ESO-provided CI secrets, runtime AWS access (Bedrock IRSA, CNPG Postgres, Valkey), and a pointer to bitovi-platform-services for the Argo/chart definitions.

No emojis; no changes below the fork section.

Documents how the claude-usage-proxy deployment actually works now that
it runs on the platform (EKS/Argo CD): image releases via v* tags off
litellm_internal_staging (self-committing image.tag to platform-deploy),
LiteLLM config changes via bitovi/claude-usage-proxy PRs, infra-shape
changes via deploy/values.yaml + staging->platform-deploy merge. Placed
above the upstream README content, clearly marked as fork-specific.
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