Add support for api_key #116

[andresC98]

Type of change

• New feature (non-breaking change which adds functionality)

Description

This pull request introduces API key authentication for the vLLMClient. This allows inference-perf to connect to vLLM server instances that are protected and require an Authorization header for requests.

Changes Implemented

• inference_perf/client/modelserver/vllm_client.py:

  • The __init__ method of VLLMClient has been updated to accept an optional api_key argument.
  • In the process_request method, an Authorization header with a Bearer token is now added to the request if an api_key was provided during client initialization.

• inference_perf/main.py:

  • The VLLMClient is now instantiated with the api_key from the server configuration (config.server.api_key), enabling the feature to be configured directly from the main config file.

This change is backward-compatible and will not affect connections to vLLM servers that do not require authentication.

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: andresC98 / name: Andres Carrillo (8644a55, faf53aa, 06f418b)

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: andresC98
Once this PR has been reviewed and has the lgtm label, please assign jeffwan for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-ci-robot]

Welcome @andresC98!

It looks like this is your first PR to kubernetes-sigs/inference-perf 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/inference-perf has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[achandrasekar]

Please resolve the merge conflict