Skip to content

update: bump version for GIE to latest 1.3.0 - #196

Closed
zdtsw wants to merge 1 commit into
llm-d-incubation:mainfrom
zdtsw:chore_4
Closed

update: bump version for GIE to latest 1.3.0#196
zdtsw wants to merge 1 commit into
llm-d-incubation:mainfrom
zdtsw:chore_4

Conversation

@zdtsw

@zdtsw zdtsw commented Jan 29, 2026

Copy link
Copy Markdown
Contributor

Description

  • currently on 0.3.0 which is old, we should get the new one esp. API version changes in inferencepool
  • this is mostly for internal GH action tests, and documentation, no real code update, thus not bump chart version

- currently on 0.3.0 is old, we should get the new one esp. API changes
  in inferencepool

Signed-off-by: Wen Zhou <wenzhou@redhat.com>

# Install Kubernetes Gateway API Inference Extension CRDs
VERSION=v0.3.0
VERSION=v1.3.0

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since modelservice no longer configures the GAIE, is the step to install CRDs (lines 54 to 62) needed at all?

@jgchn

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i have made the removal in #197 with a bunch of other small changes in github action

@kalantar

Copy link
Copy Markdown
Collaborator

Superseded by #197

@kalantar kalantar closed this Jan 29, 2026
@zdtsw

zdtsw commented Jan 29, 2026

Copy link
Copy Markdown
Contributor Author

Superseded by #197

do we still want the change for the rest part (get rid of the old API in example) ? or i can open a new PR on that

@kalantar

Copy link
Copy Markdown
Collaborator

Superseded by #197

do we still want the change for the rest part (get rid of the old API in example) ? or i can open a new PR on that

Good catch. Yes, please do.

@zdtsw

zdtsw commented Jan 29, 2026

Copy link
Copy Markdown
Contributor Author

Superseded by #197

do we still want the change for the rest part (get rid of the old API in example) ? or i can open a new PR on that

Good catch. Yes, please do.

follow up in #199

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants