generated from camel.apache.org/component
Update wiki Home page for kserve
parent
cbbe2d646a
commit
4dfa41472b
40
Home.md
40
Home.md
@ -1,21 +1,33 @@
|
||||
# Deploy the Project on CamelX Platform
|
||||
# KServe
|
||||
|
||||
Deploy on CamelX Platform in three steps
|
||||
Provide access to AI model servers with the KServe standard to run inference with remote models
|
||||
|
||||
## Step 1: Create a release
|
||||
From the project space, click on **"Create a release"**
|
||||
## Metadata
|
||||
|
||||
The new version is automatically available in the list
|
||||
| Property | Value |
|
||||
|----------|-------|
|
||||
| Scheme | `kserve` |
|
||||
| Support Level | Preview |
|
||||
| Labels | ai |
|
||||
| Version | 4.10.2 |
|
||||
|
||||
## Step 2: Deploy
|
||||
Click on **"Deploy"**
|
||||
## Maven Dependency
|
||||
|
||||
- **Version:** Select the desired release
|
||||
- **Environment:** Choose `Development`, `Staging`, or `Production`
|
||||
- **Configuration:** Select the configuration source
|
||||
- **Resources:** Set CPU and Memory
|
||||
```xml
|
||||
<dependency>
|
||||
<groupId>org.apache.camel</groupId>
|
||||
<artifactId>camel-kserve</artifactId>
|
||||
<version>4.10.2</version>
|
||||
</dependency>
|
||||
```
|
||||
|
||||
## Step 3: Expose
|
||||
Enable **"Expose"**
|
||||
## Endpoint Properties
|
||||
|
||||
Choose an **API Gateway** (Internal, Public, etc.)
|
||||
| Name | Type | Required | Default | Description |
|
||||
|------|------|----------|---------|-------------|
|
||||
| `api` | string | ✓ | | The KServe API |
|
||||
| `modelName` | string | | | The name of the model used for inference. |
|
||||
| `modelVersion` | string | | | The version of the model used for inference. |
|
||||
| `target` | string | | `localhost:8001` | The target URI of the client. See: https://grpc.github.io/grpc-java/javadoc/io/grpc/Grpc.html#newChannelBuilder%28java.lang.String,io.grpc.ChannelCredentials%29 |
|
||||
| `lazyStartProducer` | boolean | | `false` | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. |
|
||||
| `credentials` | object | | | The credentials of the client. |
|
||||
|
||||
Loading…
Reference in New Issue
Block a user