-
Notifications
You must be signed in to change notification settings - Fork 68
Fix agentgateway release pin #1476
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
Draft
danehans
wants to merge
2
commits into
NVIDIA:main
Choose a base branch
from
danehans:fix-agentgateway-release-pin
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Confirmed at 1192ddb: this pins the agentgateway controller to v1.3.1 while the component still vendors the Inference Extension v1.3.0 CRDs (inference-extension-crds.yaml), whose
InferencePoolschema lacksspec.appProtocol. agentgateway v1.3.1 builds against inference-extension v1.5.0 (go.mod) and mapskubernetes.io/h2cto HTTP/2, defaulting to HTTP/1.1 (controller/pkg/syncer/service.go). With the v1.3.0 schema installed, a user-setappProtocol: kubernetes.io/h2cis rejected under strict validation or, if admitted, pruned; in the latter case the controller silently falls back to HTTP/1.1.This is a missed new capability rather than a regression — the previous v2.2.1 pin was a transitional artifact published from the kgateway v2.2.1 release, whose controller hardcoded HTTP/1.1 — so it need not block this PR; a coordinated follow-up works.
If the follow-up vendors the v1.5.0 CRDs, note the v1.5.0 bundle drops
inferencepools.inference.networking.x-k8s.io, so these must switch toinferencepools.inference.networking.k8s.ioin the same PR:recipes/checks/agentgateway-crds/health-check.yaml:158tests/chainsaw/ai-conformance/cluster/assert-crds.yaml:55tests/chainsaw/ai-conformance/kind-inference-dynamo/assert-crds.yaml:53validators/conformance/inference_gateway_check.go:128(requiredCRDs)One upgrade caveat, scoped to hook-based vendored deployments: plain Helm/Helmfile vendored bundles encode supplemental manifests as post-install hooks, which are not rerun on upgrade, so the entire v1.3 CRD bundle can remain stale on upgraded clusters. Tracked Helm releases and Flux post HelmReleases reconcile removals; vendored Argo hook lifecycle needs separate validation.