You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: site-src/guides/index.md
+58-41
Original file line number
Diff line number
Diff line change
@@ -7,11 +7,12 @@
7
7
This quickstart guide is intended for engineers familiar with k8s and model servers (vLLM in this instance). The goal of this guide is to get an Inference Gateway up and running!
8
8
9
9
## **Prerequisites**
10
-
- A cluster with:
11
-
- Support for services of type `LoadBalancer`. (This can be validated by ensuring your Envoy Gateway is up and running).
12
-
For example, with Kind, you can follow [these steps](https://kind.sigs.k8s.io/docs/user/loadbalancer).
13
-
- Support for [sidecar containers](https://kubernetes.io/docs/concepts/workloads/pods/sidecar-containers/) (enabled by default since Kubernetes v1.29)
14
-
to run the model server deployment.
10
+
11
+
- A cluster with:
12
+
- Support for services of type `LoadBalancer`. For kind clusters, follow [this guide](https://kind.sigs.k8s.io/docs/user/loadbalancer)
13
+
to get services of type LoadBalancer working.
14
+
- Support for [sidecar containers](https://kubernetes.io/docs/concepts/workloads/pods/sidecar-containers/) (enabled by default since Kubernetes v1.29)
15
+
to run the model server deployment.
15
16
16
17
## **Steps**
17
18
@@ -105,6 +106,24 @@ This quickstart guide is intended for engineers familiar with k8s and model serv
4. Confirm that the HTTPRoute status conditions include `Accepted=True` and `ResolvedRefs=True`:
116
+
117
+
```bash
118
+
kubectl get httproute llm-route -o yaml
119
+
```
120
+
121
+
5. Given that the default connection timeout may be insufficient for most inference workloads, it is recommended to configure a timeout appropriate for your intended use case.
1. If you run the Endpoint Picker (EPP) with the `--secureServing` flag set to `true` (the default mode), it is currently using a self-signed certificate. As a security measure, Istio does not trust self-signed certificates by default. As a temporary workaround, you can apply the destination rule to bypass TLS verification for EPP. A more secure TLS implementation in EPP is being discussed in [Issue 582](https://github.com/kubernetes-sigs/gateway-api-inference-extension/issues/582).
153
+
3. If you run the Endpoint Picker (EPP) with the `--secureServing` flag set to `true` (the default mode), it is currently using a self-signed certificate. As a security measure, Istio does not trust self-signed certificates by default. As a temporary workaround, you can apply the destination rule to bypass TLS verification for EPP. A more secure TLS implementation in EPP is being discussed in [Issue 582](https://github.com/kubernetes-sigs/gateway-api-inference-extension/issues/582).
7. Confirm that the HTTPRoute status conditions include `Accepted=True` and `ResolvedRefs=True`:
185
+
186
+
```bash
187
+
kubectl get httproute llm-route -o yaml
188
+
```
189
+
159
190
=== "Kgateway"
160
191
161
-
[Kgateway](https://kgateway.dev/) v2.0.0 adds support for inference extension as a **technical preview**. This means do not
192
+
[Kgateway](https://kgateway.dev/) recently added support for inference extension as a **technical preview**. This means do not
162
193
run Kgateway with inference extension in production environments. Refer to [Issue 10411](https://github.com/kgateway-dev/kgateway/issues/10411)
163
194
for the list of caveats, supported features, etc.
164
195
@@ -167,20 +198,20 @@ This quickstart guide is intended for engineers familiar with k8s and model serv
Given that default timeouts for above implementations may be insufficient for most inference workloads, it is recommended to configure a timeout appropriate for your intended use case.
0 commit comments