You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
bug(manifests): milvus-deployment.yaml is a live Pod state dump, not an applicable Deployment manifest #171
manifests/milvus-deployment.yaml is named as a Deployment but contains a raw kubectl get pod -o yaml output from a live cluster. It cannot be applied to any new cluster.
Root Cause
The file contains cluster-runtime fields that are meaningless outside the original cluster:
kind: Pod with a ReplicaSet-generated name (milvus-standalone-final-5cb655b8d6-6ngrn)
uid, resourceVersion, ownerReferences pointing to a non-existent ReplicaSet
nodeName: 10.0.10.183 pinning the Pod to a specific node
Full status block with live containerID hashes, pod IPs, and timestamps
kubectl apply -f manifests/milvus-deployment.yaml fails on any cluster other than the original. Contributors following the README cannot deploy Milvus using this file.
Proposed Fix
Replace with a clean Deployment manifest preserving the three-container spec (milvus, etcd, minio) but removing all cluster-runtime fields.
Activity
zong0728 commentedon Mar 23, 2026
/assign
chasecadet commentedon Nov 20, 2026
Thank you for reporting this!
We are closing pre-restructure issues targeting the legacy
server/,server-https/,manifests/,kagent-feast-mcp/, or in-processSentenceTransformerprototype code. In #207, #210, #233, #240, and #249,kubeflow/docs-agentmigrated to dedicated TEI (text-embeddings-inference), FastMCP (docs-agent-mcp/mcp-server/), shared modular KFP pipelines (docs-agent-mcp/pipelines/), and Helm charts (docs-agent-mcp/charts/).If you still observe an equivalent issue on the current
mainstack, please feel free to open a new issue using the current issue templates.