[Feature]: Run a services-only PAIR node as a container or Kubernetes pod
維護者通常 5 天內回覆
@sherief-nv 已經在處理了。
開始於 2026年9月9日。
評估
這個 Issue 還沒有評估資料。
描述
Area
Terminal / headless operation
User problem
A workload running on a Kubernetes cluster (a web app, a cron job, an agent) wants to use PAIR's endpoint, but PAIR runs on desktops and there is no documented way to put a node on the cluster. The two obvious attempts fail: a container on the pod network discovers nothing, because mDNS never leaves the local link; and pointing the workload at a node elsewhere on the LAN returns 403 loopback-only, by design.
Desired outcome
A documented, supported way to run a services-only node as a container, and as a pod on Kubernetes, that joins an existing cluster and gives the cluster's workloads an OpenAI-compatible endpoint that routes to the nodes with engines. Concretely: a Dockerfile built from the release asset, a page in docs/ that explains host networking and the loopback relay, and reference manifests.
Alternatives considered
- Issuing in-cluster workloads mTLS client certificates so they can talk to a node's TLS personality directly. Rejected: that hands out a cluster identity per consumer.
- Running the node on the Kubernetes host outside Kubernetes (systemd). Works, but is invisible to the cluster's scheduling, policy and lifecycle, and needs a relay anyway.
Additional context
CONTRIBUTING.md asks for maintainer alignment before adding a distribution channel. I have a validated implementation (PAIR v0.1.1 on OpenShift 4.22 with OVN-Kubernetes, paired with a Linux GPU node and a macOS node, five-minute soak with no failed requests) and will open it as a documentation PR with the files under services/container/. Happy to adjust the base image, drop the Dockerfile and keep only the page, or port the relay to Go if that is what you would accept.
Related: #30 fixes the address a node on an OVN-Kubernetes host advertises, which this work uncovered.
- 主要語言
- Go
- 星號
- 1.6k
- 分支
- 266
- 平均合併
- 3 天 15 小時
- 30 天內合併 PR
- 23
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
NVIDIA/Personal-AI-Router 的其他 Issue
-
enhancement
難度 4/5 一週以上 新手友好度 12/100
NVIDIA/Personal-AI-Router#162 ·
維護者通常 5 天內回覆
-
enhancement
難度 4/5 3-5 天 新手友好度 25/100
NVIDIA/Personal-AI-Router#154 · 1 則留言 ·
維護者通常 5 天內回覆
-
[Feature]: [Ollama] Alert the user about model pull failures可能已有人在做 @ckelseynv 於 2 天前認領。 未關閉enhancement
難度 3/5 1-2 天 新手友好度 56/100
NVIDIA/Personal-AI-Router#152 · 1 則留言 · 已指派 1 人 ·
維護者通常 5 天內回覆
-
[Bug]: /v1/responses bypasses model-owner filtering in the Ollama proxy可能已有人在做 @ilaigold 於 3 天前認領。 未關閉
難度 3/5 半天 新手友好度 84/100
NVIDIA/Personal-AI-Router#146 ·
維護者通常 5 天內回覆
-
Make model download cancellation asynchronous可能已有人在做 @ckelseynv 於 19 天前認領。 未關閉enhancement
NVIDIA/Personal-AI-Router#115 · 已指派 1 人 ·
維護者通常 5 天內回覆
查看 NVIDIA/Personal-AI-Router 的全部 Issue
相似的 Issue
-
[schema-coverage] elasticstack_kibana_security_detection_rule可能已有人在做 @github-actions 今天認領。 未關閉acceptance-tests phase-coding schema-coverage testing triaged
難度 2/5 1-3 小時 新手友好度 65/100
elastic/terraform-provider-elasticstack#5186 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 78/100
jaegertracing/jaeger#9830 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 76/100
apache/rocketmq-dashboard#6318 ·
維護者通常 5 天內回覆
-
難度 2/5 1-3 小時 新手友好度 84/100
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 83/100
GoogleCloudPlatform/opentelemetry-operations-collector#710 ·
維護者通常 1 天內回覆