Ilker ManapandClaude Opus 5.5
bae16426a2
A bundle carries what a cluster would download — llmgw's release with its signed checksums, every llama.cpp build per architecture with GitHub's checksums, model files pinned and checked against Hugging Face's — into a directory or a tar whose manifest sha256 is carried apart. Import checks everything, the release against the signing key, before anything is put in the mirror. With offline.mirror set, nodes install llama.cpp from the mirror against checksums the control plane holds and sends over the agent stream; releases default to the mirror for node add, ctl upgrade and agent upgrades. server init and the setup form install from a bundle. The Helm chart runs one control plane with SQLite on a claim or an external PostgreSQL, Secrets for the agent certificate and admin token, Services, Ingress and ServiceMonitor; deploy/container/Dockerfile builds its image. GPU nodes stay outside Kubernetes, as docs/kubernetes.md explains. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
18 lines
517 B
YAML
18 lines
517 B
YAML
apiVersion: v2
|
|
name: llmgw
|
|
description: >-
|
|
The llmgw control plane — the OpenAI-compatible gateway, the router and the
|
|
scheduler that places models on GPU and CPU nodes. The nodes themselves run
|
|
outside Kubernetes; see docs/kubernetes.md.
|
|
type: application
|
|
# The chart's own version; appVersion is the llmgw release the image holds.
|
|
version: 0.1.0
|
|
appVersion: "v0.11.1"
|
|
home: https://gitea.mynodes.xyz/ilker/llmgw
|
|
sources:
|
|
- https://gitea.mynodes.xyz/ilker/llmgw
|
|
keywords:
|
|
- llm
|
|
- gateway
|
|
- inference
|