Skip to content

Latest commit

 

History

History
36 lines (23 loc) · 1.31 KB

_index.md

File metadata and controls

36 lines (23 loc) · 1.31 KB

Model Delivery

ModelArtifact gives a model version a stable identity. Its delivery can be handled by the engine, a node cache, a PVC or an image.

Follow the Model Prefetch Walkthrough for a complete example with captured CR output.

Contents

Sources and delivery

Model Artifact covers resolution, validation and the delivery choices. Model Image Source covers image-backed weights.

Cache operations

Model Store Operations covers configuration, watermarks and removal. Model Prefetch covers warming weights before a Pod needs them. Node Model Store describes the per-node record and plugin.

Observing and syncing

The Model Artifact API covers reading artifact progress and node caches from the API. Node-to-Node Sync covers how a node pulls weights from another node's cache.


See also — Model Deployment (serving a model) · GPU Instances (using weights in an Instance)

Next → Model Artifact — choose a source and delivery.