Bug Description
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 ReplicaSetnodeName: 10.0.10.183 pinning the Pod to a specific node- Full
status block with live containerID hashes, pod IPs, and timestamps
- Auto-injected
kube-api-access-2hjlp projected volume
Impact
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.
I will submit a PR with this fix.
Bug Description
manifests/milvus-deployment.yamlis named as a Deployment but contains a rawkubectl get pod -o yamloutput 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: Podwith a ReplicaSet-generated name (milvus-standalone-final-5cb655b8d6-6ngrn)uid,resourceVersion,ownerReferencespointing to a non-existent ReplicaSetnodeName: 10.0.10.183pinning the Pod to a specific nodestatusblock with livecontainerIDhashes, pod IPs, and timestampskube-api-access-2hjlpprojected volumeImpact
kubectl apply -f manifests/milvus-deployment.yamlfails on any cluster other than the original. Contributors following the README cannot deploy Milvus using this file.Proposed Fix
Replace with a clean
Deploymentmanifest preserving the three-container spec (milvus, etcd, minio) but removing all cluster-runtime fields.I will submit a PR with this fix.