-
Notifications
You must be signed in to change notification settings - Fork 804
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Kubernetes deployment guide #899
Open
terrytangyuan
wants to merge
3
commits into
meta-llama:main
Choose a base branch
from
terrytangyuan:k8s-deployment
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+214
−1
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,207 @@ | ||
# Kubernetes Deployment Guide | ||
|
||
Instead of starting the Llama Stack and vLLM servers locally. We can deploy them in a Kubernetes cluster. In this guide, we'll use a local [Kind](https://kind.sigs.k8s.io/) cluster and a vLLM inference service in the same cluster for demonstration purposes. | ||
|
||
First, create a local Kubernetes cluster via Kind: | ||
|
||
```bash | ||
kind create cluster --image kindest/node:v1.32.0 --name llama-stack-test | ||
``` | ||
|
||
Start vLLM server as a Kubernetes Pod and Service: | ||
|
||
```bash | ||
cat <<EOF |kubectl apply -f - | ||
apiVersion: v1 | ||
kind: PersistentVolumeClaim | ||
metadata: | ||
name: vllm-models | ||
spec: | ||
accessModes: | ||
- ReadWriteOnce | ||
volumeMode: Filesystem | ||
resources: | ||
requests: | ||
storage: 50Gi | ||
--- | ||
apiVersion: v1 | ||
kind: Secret | ||
metadata: | ||
name: hf-token-secret | ||
type: Opaque | ||
data: | ||
token: $(HF_TOKEN) | ||
--- | ||
apiVersion: apps/v1 | ||
kind: Deployment | ||
metadata: | ||
name: vllm-server | ||
spec: | ||
replicas: 1 | ||
selector: | ||
matchLabels: | ||
app.kubernetes.io/name: vllm | ||
template: | ||
metadata: | ||
labels: | ||
app.kubernetes.io/name: vllm | ||
spec: | ||
containers: | ||
- name: llama-stack | ||
image: $(VLLM_IMAGE) | ||
command: | ||
- bash | ||
- -c | ||
- | | ||
MODEL="meta-llama/Llama-3.2-1B-Instruct" | ||
MODEL_PATH=/app/model/$(basename $MODEL) | ||
huggingface-cli login --token $HUGGING_FACE_HUB_TOKEN | ||
huggingface-cli download $MODEL --local-dir $MODEL_PATH --cache-dir $MODEL_PATH | ||
python3 -m vllm.entrypoints.openai.api_server --model $MODEL_PATH --served-model-name $MODEL --port 8000 | ||
ports: | ||
- containerPort: 8000 | ||
volumeMounts: | ||
- name: llama-storage | ||
mountPath: /app/model | ||
env: | ||
- name: HUGGING_FACE_HUB_TOKEN | ||
valueFrom: | ||
secretKeyRef: | ||
name: hf-token-secret | ||
key: token | ||
volumes: | ||
- name: llama-storage | ||
persistentVolumeClaim: | ||
claimName: vllm-models | ||
--- | ||
apiVersion: v1 | ||
kind: Service | ||
metadata: | ||
name: vllm-server | ||
spec: | ||
selector: | ||
app.kubernetes.io/name: vllm | ||
ports: | ||
- protocol: TCP | ||
port: 8000 | ||
targetPort: 8000 | ||
type: ClusterIP | ||
EOF | ||
``` | ||
|
||
We can verify that the vLLM server has started successfully via the logs (this might take a couple of minutes to download the model): | ||
|
||
```bash | ||
$ kubectl logs -l app.kubernetes.io/name=vllm | ||
... | ||
INFO: Started server process [1] | ||
INFO: Waiting for application startup. | ||
INFO: Application startup complete. | ||
INFO: Uvicorn running on http://0.0.0.0:8000 (Press CTRL+C to quit) | ||
``` | ||
|
||
Then we can modify the Llama Stack run configuration YAML with the following inference provider: | ||
|
||
```yaml | ||
providers: | ||
inference: | ||
- provider_id: vllm | ||
provider_type: remote::vllm | ||
config: | ||
url: http://vllm-server.default.svc.cluster.local:8000/v1 | ||
max_tokens: 4096 | ||
api_token: fake | ||
``` | ||
|
||
Once we have defined the run configuration for Llama Stack, we can build an image with that configuration and the server source code: | ||
|
||
```bash | ||
cat >/tmp/test-vllm-llama-stack/Containerfile.llama-stack-run-k8s <<EOF | ||
FROM distribution-myenv:dev | ||
|
||
RUN apt-get update && apt-get install -y git | ||
RUN git clone https://github.com/meta-llama/llama-stack.git /app/llama-stack-source | ||
|
||
ADD ./vllm-llama-stack-run-k8s.yaml /app/config.yaml | ||
EOF | ||
podman build -f /tmp/test-vllm-llama-stack/Containerfile.llama-stack-run-k8s -t llama-stack-run-k8s /tmp/test-vllm-llama-stack | ||
``` | ||
|
||
|
||
We can then start the Llama Stack server by deploying a Kubernetes Pod and Service: | ||
|
||
```bash | ||
cat <<EOF |kubectl apply -f - | ||
apiVersion: v1 | ||
kind: PersistentVolumeClaim | ||
metadata: | ||
name: llama-pvc | ||
spec: | ||
accessModes: | ||
- ReadWriteOnce | ||
resources: | ||
requests: | ||
storage: 1Gi | ||
--- | ||
apiVersion: apps/v1 | ||
kind: Deployment | ||
metadata: | ||
name: llama-stack-server | ||
spec: | ||
replicas: 1 | ||
selector: | ||
matchLabels: | ||
app.kubernetes.io/name: llama-stack | ||
template: | ||
metadata: | ||
labels: | ||
app.kubernetes.io/name: llama-stack | ||
spec: | ||
containers: | ||
- name: llama-stack | ||
image: localhost/llama-stack-run-k8s:latest | ||
imagePullPolicy: IfNotPresent | ||
command: ["python", "-m", "llama_stack.distribution.server.server", "--yaml-config", "/app/config.yaml"] | ||
ports: | ||
- containerPort: 5000 | ||
volumeMounts: | ||
- name: llama-storage | ||
mountPath: /root/.llama | ||
volumes: | ||
- name: llama-storage | ||
persistentVolumeClaim: | ||
claimName: llama-pvc | ||
--- | ||
apiVersion: v1 | ||
kind: Service | ||
metadata: | ||
name: llama-stack-service | ||
spec: | ||
selector: | ||
app.kubernetes.io/name: llama-stack | ||
ports: | ||
- protocol: TCP | ||
port: 5000 | ||
targetPort: 5000 | ||
type: ClusterIP | ||
EOF | ||
``` | ||
|
||
We can check that the LlamaStack server has started: | ||
|
||
```bash | ||
$ kubectl logs -l app.kubernetes.io/name=llama-stack | ||
... | ||
INFO: Started server process [1] | ||
INFO: Waiting for application startup. | ||
INFO: ASGI 'lifespan' protocol appears unsupported. | ||
INFO: Application startup complete. | ||
INFO: Uvicorn running on http://['::', '0.0.0.0']:5000 (Press CTRL+C to quit) | ||
``` | ||
|
||
Finally, we forward the Kubernetes service to a local port and test some inference requests against it via the Llama Stack Client: | ||
|
||
```bash | ||
kubectl port-forward service/llama-stack-service 5000:5000 | ||
llama-stack-client --endpoint http://localhost:5000 inference chat-completion --message "hello, what model are you?" | ||
``` |
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's an open question to me as to whether or not Kubernetes maps to the Llama Stack "distribution" concept. Many of these steps would not hold true for running w/ meta-reference or ollama. This feels like a sibling of https://github.com/meta-llama/llama-stack/blob/39c34dd25f9365b09000a07de5c46dbdba27e3cb/distributions/remote-vllm/compose.yaml.
However, there is substantial overlap between the compose files for each distribution, so I think we can do better. I think we probably need to figure out how to draw the right boundaries around distributions and deployment options. In the meantime, WDYT about moving this there?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We were discussing the same idea on Discord. My initial thought was to first provide a guide so that others can start following similar ways to deploy their selected providers to K8s (and make any necessary changes to meet their needs). Next step is to provide a packaged YAML file that's templated for K8s deployment for each provider (e.g. remote:vllm) and then we can simplify this guide. I believe we'll need a guide anyways to call out specific details.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll leave this call to the maintainers :)