Skip to content

logfire-0.13.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 13 Mar 19:59
logfire-0.13.0
cd1d755
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Summary

  • Added Pydantic AI Gateway deployment (opt-in, disabled by default — set logfire-ai-gateway.enabled: true to deploy)

  • Added Remote MCP deployment

  • Removed filter cache deployment

    Upgrade notes

    • The AI Gateway is disabled by default. To enable it, set logfire-ai-gateway.enabled: true.
    • To manage the AI Gateway secrets externally (e.g. via Argo CD or an external secret manager), set existingGatewaySecret.enabled: true and existingGatewaySecret.name to the name of a pre-existing
      Kubernetes Secret containing a key (url-safe base64-encoded 32-byte encryption key) and an internalSecret (arbitrary shared secret string).
      existingGatewaySecret is only evaluated when logfire-ai-gateway.enabled: true.

    Breaking changes

    If you use existingSecret.enabled: true, you must add logfire-mcp-oauth-client-secret to the Secret named by existingSecret.name (otherwise the backend pod won't start).

  • Generate a compatible value: head -c 32 /dev/urandom | base64 | head -c 32

  • Put it in the Secret as stringData.logfire-mcp-oauth-client-secret: "<the value>".

    If you don't use existingSecret, no action required (the chart creates the logfire-mcp-oauth-client-secret Secret automatically).

PR: #137

Helm chart for self-hosted Pydantic Logfire

Assets 3
Loading