Add support for GKE Gateway API #359
Merged
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.
This pull request introduces support for Google Kubernetes Engine (GKE) Gateway API implementations, enabling users to leverage GKE's native L7 load balancers for both internal and regional external traffic.
GKE Gateway Policies:
Integrates GCPBackendPolicy and HealthCheckPolicy resources into the Helm chart for the sample application.
These GKE-specific policies are now conditionally created only when the gateway.gatewayClassName is set to a GKE type (e.g., gke-l7-rilb).
Installer Script Update:
The llmd-installer.sh validation logic has been updated to recognize gke-l7-rilb and gke-l7-regional-external-managed as valid gateway types.
install.log
Following presets are available to your users: