Skip to content

bug(manifests): milvus-deployment.yaml is a live Pod state dump, not an applicable Deployment manifest #171

Closed as not planned

Description

@zong0728

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 ReplicaSet
  • nodeName: 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.

Activity

  1. zong0728 commented on Mar 23, 2026

    @zong0728
    Author

    /assign

  2. chasecadet commented on Nov 20, 2026

    @chasecadet
    Contributor

    Thank you for reporting this!

    We are closing pre-restructure issues targeting the legacy server/, server-https/, manifests/, kagent-feast-mcp/, or in-process SentenceTransformer prototype code. In #207, #210, #233, #240, and #249, kubeflow/docs-agent migrated 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 main stack, please feel free to open a new issue using the current issue templates.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions