Skip to content

577 - Add version specifier for Envoy Gateway at v1.3.0 #578

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.

Sign up for GitHub

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
cjohannsen-cloudera wants to merge 1 commit into
base: main
Choose a base branch
from
Open

577 - Add version specifier for Envoy Gateway at v1.3.0 #578

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/admin-guide/gatewayapi-migration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -35,7 +35,7 @@ kubectl apply -f https://github.com/kubernetes-sigs/gateway-api/releases/downloa

## 2. Create GatewayClass

Create a `GatewayClass` resource using your preferred network controller. For this example, we will use [Envoy Gateway](https://gateway.envoyproxy.io/docs/) as the network controller.
Create a `GatewayClass` resource using your preferred network controller. For this example, we will use [Envoy Gateway](https://gateway.envoyproxy.io/docs/) as the network controller. **Note:** Kserve requires Envoy Gateway **v1.3.0**.
Copy link
Contributor

@Jooho Jooho Jan 29, 2026

Choose a reason for hiding this comment

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

We are using 1.5.0 now (https://github.com/kserve/kserve/blob/master/kserve-deps.env#L18C1-L18C22)

We now centralized all the dependencies in a single file in kserve so I think we need some automation to update this version based on the file

Copy link
Member

@pierDipi pierDipi Jan 29, 2026

Choose a reason for hiding this comment

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

I think we're trying to describe the minimum version?

Copy link
Contributor Author

@cjohannsen-cloudera cjohannsen-cloudera Jan 29, 2026

Choose a reason for hiding this comment

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

This applies specifically to Kserve 0.16. Mainline uses more updated versions and this will need to be changed when we perform a release.

Copy link
Member

@sivanantha321 sivanantha321 Feb 2, 2026

Choose a reason for hiding this comment

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

If it is for 0.16, then it should be updated here. The src/ dir for the nightly version (latest master).

Copy link
Contributor

@spolti spolti Feb 20, 2026

Choose a reason for hiding this comment

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

isn't the 0.16 using v1.2.2? https://github.com/kserve/kserve/blob/release-0.16/kserve-deps.env#L17C12-L17C29

Copy link
Contributor

@spolti spolti Feb 20, 2026

Choose a reason for hiding this comment

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

Suggested change
Create a `GatewayClass` resource using your preferred network controller. For this example, we will use [Envoy Gateway](https://gateway.envoyproxy.io/docs/) as the network controller. **Note:** Kserve requires Envoy Gateway **v1.3.0**.
Create a `GatewayClass` resource using your preferred network controller. For this example, we will use [Envoy Gateway](https://gateway.envoyproxy.io/docs/) as the network controller. **Note:** KServe requires Envoy Gateway **v1.3.0**.


```yaml
apiVersion: gateway.networking.k8s.io/v1
Expand Down