Skip to content

"Getting started with Gateway API Inference Extension" guide not working #476

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
pabloheiber opened this issue Mar 11, 2025 · 1 comment
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@pabloheiber
Copy link

What happened:

I tried to set up Gateway API Inteference Extension following https://gateway-api-inference-extension.sigs.k8s.io/guides/

I used the GPU-based version.

What you expected to happen:

When getting to the step "Confirm that the Gateway was assigned an IP address and reports a Programmed=True status:" I was expecting to confirm as advertised, but I got an unexpected output from the command:

$ kubectl get gateway inference-gateway
NAME                CLASS               ADDRESS   PROGRAMMED   AGE
inference-gateway   inference-gateway             False        10s
$ kubectl get gateway inference-gateway
NAME                CLASS               ADDRESS   PROGRAMMED   AGE
inference-gateway   inference-gateway             False        39s
$ kubectl get gateway inference-gateway
NAME                CLASS               ADDRESS   PROGRAMMED   AGE
inference-gateway   inference-gateway          

How to reproduce it (as minimally and precisely as possible):

Follow the guide to the letter.

Anything else we need to know?:

Environment:

  • Kubernetes version (use kubectl version):
$ kubectl version
Client Version: v1.31.6-dispatcher
Kustomize Version: v5.4.2
Server Version: v1.31.5-gke.1233000
  • Inference extension version (use git describe --tags --dirty --always): N/A
  • Cloud provider or hardware configuration: Google Cloud
  • Install tools:
  • Others:
@pabloheiber pabloheiber added the kind/bug Categorizes issue or PR as related to a bug. label Mar 11, 2025
@kfswain
Copy link
Collaborator

kfswain commented Apr 22, 2025

Did we ever get this resolved @pabloheiber? We have made quite a bit of updates to our documentation

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

2 participants