Uploaded image for project: 'OpenShift Request For Enhancement'
  1. OpenShift Request For Enhancement
  2. RFE-8564

[RFE] Add optional tracking header to the OLS Custom Resource

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • Lightspeed
    • None
    • None
    • Product / Portfolio Work
    • None
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Currently, there is no way to distinguish individual user usage when OpenShift Lightspeed (OLS) makes requests to the LLM provider.

      This creates the following issues:

      • Cost Allocation: not possible to track which users or teams are consuming the most tokens.
      • Rate Limiting: not possible to apply rate limits per user (e.g., via LiteLLM) to prevent a single user from draining the organization's quota.

      This configuration should allow to specify a custom HTTP header key (e.g., x-user-id or llm-user) that OLS will inject into every request sent to the LLM provider. Crucially, the value of this header should automatically populate with the authenticated OpenShift user's ID or username.

      A proposal for doing it could be something similar to:

      spec:
        llm:
          providers:
            - name: my-provider
              forward_authenticated_user_header: "X-User-ID" # NEW REQUESTED FEATURE
      

              gausingh@redhat.com Gaurav Singh
              rhn-support-emahoney Evan Mahoney
              None
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                None
                None