Reduced GPU requirements

[anshuman-agarwala]

Fixes #253

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: anshuman-agarwala
Once this PR has been reviewed and has the lgtm label, please assign ahg-g 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 @anshuman-agarwala!

It looks like this is your first PR to kubernetes-sigs/gateway-api-inference-extension 🎉. 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/gateway-api-inference-extension 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. 😃

[k8s-ci-robot]

Hi @anshuman-agarwala. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[netlify]

✅ Deploy Preview for gateway-api-inference-extension ready!

Name	Link
🔨 Latest commit	95ddf2e
🔍 Latest deploy log	https://app.netlify.com/sites/gateway-api-inference-extension/deploys/67a048a57bb1e300089a8536
😎 Deploy Preview	https://deploy-preview-272--gateway-api-inference-extension.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[liu-cong]

with only 1 replica you cannot really see the benefits of the request scheduling algorithms. let's keep 3?

[kfswain]

Big plus 1 here. While I understand the desire to minimize the accelerator footprint of a getting started guide. Someone interested in an inference-tailored scheduling tool will have access to multiple accelerators to test this.

We should add comments clarifying why we are reducing the max-loras also. (L4s need this, but A100/H100s can go higher)

[danehans]

I agree with ^. However, we need a simple mechanism, e.g. kustomize, to allow users to change the default 3 to 1 or any other value. I've been using 1 in my test/dev env and can at least see the LoRA load balancing for my single node kind cluster. For example, create a kustomization.yaml file in pkg/manifests/vllm/:

apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization
resources:
  - deployment.yaml
replicas:
  - name: vllm-llama2-7b-pool
    count: 1

Run kubectl apply -k pkg/manifests/vllm/ and the vllm deployment will be run with 1 replica.

[danehans]

This PR and associated issue may no longer be required due to #259 (comment). I'm in the process of testing and will provide an update shortly.

/hold

[ahg-g]

Closing for now