有人在本地 kubernetes 集群上部署 Milvus 吗?

发布于 2025-01-11 14:13:23 字数 2757 浏览 0 评论 0原文

我想将 Milvus 部署到我的本地 kubernetes 集群 我遵循本指南

步骤1:我使用 nfs-kernel-server 在我的服务器上设置 nfs 服务器(我也可以挂载到 pod 并挂载到同一网络中的其他机器)

第 2 步:我安装 helm Chart charts/stable/nfs-client-provisioner (我在模板文件夹中的部署末尾添加了节点选择器,以选择可以使用哪个服务器)


$ helm install nfs-client . -n milvus
  WARNING: This chart is deprecated
  NAME: nfs-client
  LAST DEPLOYED: Tue Mar  1 10:12:12 2022
  NAMESPACE: milvus
  STATUS: deployed
  REVISION: 1
  TEST SUITE: None

$ helm list -n milvus
  NAME          NAMESPACE   REVISION    UPDATED                                 STATUS      CHART                           APP VERSION
  nfs-client    milvus      1           2022-03-01 10:12:12.969901256 +0700 +07 deployed    nfs-client-provisioner-1.2.11   3.1.0

$ kubectl get pod -n milvus
  NAME                                                 READY   STATUS    RESTARTS   AGE
  nfs-client-nfs-client-provisioner-7685d96cbc-wxfkb   1/1     Running   0          6m18s

第 3 步:克隆 https://github.com/milvus-io/milvus-helm.git

$ cd milvus-helm/charts/milvus
$ helm install --set cluster.enabled=true --set persistence.enabled=true --set mysql.enabled=true my-release  . -n milvus
  NAME: my-release
  LAST DEPLOYED: Tue Mar  1 10:33:17 2022
  NAMESPACE: milvus
  STATUS: deployed
  REVISION: 1
  TEST SUITE: None
  NOTES:
  The Milvus server can be accessed via port 19530 on the following DNS name from within your cluster:
  my-release-milvus.milvus.svc.cluster.local

  Get the Milvus server URL by running these commands in the same shell:
    export POD_NAME=$(kubectl get pods --namespace milvus -l "app.kubernetes.io/name=milvus,app.kubernetes.io/instance=my-release,component=mishards" -o jsonpath="{.items[0].metadata.name}")
    kubectl --namespace milvus port-forward $POD_NAME 19530 19121

  For more information on running Milvus, visit:
  https://milvus.io/

$ kubectl get pod -n milvus
  NAME                                                 READY   STATUS     RESTARTS   AGE
  my-release-milvus-mishards-7cb6574bb5-jrcf4          0/1     Init:0/1   0          6m23s
  my-release-milvus-readonly-8588bdd49-7wtwt           0/1     Pending    0          6m23s
  my-release-milvus-writable-6db7bfc647-qrd69          0/1     Pending    0          6m23s
  my-release-mysql-5f69d5bd87-99zd5                    0/1     Pending    0          6m23s
  nfs-client-nfs-client-provisioner-7685d96cbc-wxfkb   1/1     Running    0          21m

如您所见,pod 卡住并且无法运行。有人在本地 kubernetes 集群上部署 Milvus 吗?请帮我!!!

I want to deploy Milvus to my kubernetes cluster on-premise and
I follow this guide

Step 1: I setup nfs server on my server with nfs-kernel-server (I'm able to mount to pod and mount to my other machine in the same network too)

Step 2: I install helm chart charts/stable/nfs-client-provisioner (I add the node selector in the end of deployment in template folder to choose which server can be used)


$ helm install nfs-client . -n milvus
  WARNING: This chart is deprecated
  NAME: nfs-client
  LAST DEPLOYED: Tue Mar  1 10:12:12 2022
  NAMESPACE: milvus
  STATUS: deployed
  REVISION: 1
  TEST SUITE: None

$ helm list -n milvus
  NAME          NAMESPACE   REVISION    UPDATED                                 STATUS      CHART                           APP VERSION
  nfs-client    milvus      1           2022-03-01 10:12:12.969901256 +0700 +07 deployed    nfs-client-provisioner-1.2.11   3.1.0

$ kubectl get pod -n milvus
  NAME                                                 READY   STATUS    RESTARTS   AGE
  nfs-client-nfs-client-provisioner-7685d96cbc-wxfkb   1/1     Running   0          6m18s

Step 3: Clone branch 0.11.0 of https://github.com/milvus-io/milvus-helm.git

$ cd milvus-helm/charts/milvus
$ helm install --set cluster.enabled=true --set persistence.enabled=true --set mysql.enabled=true my-release  . -n milvus
  NAME: my-release
  LAST DEPLOYED: Tue Mar  1 10:33:17 2022
  NAMESPACE: milvus
  STATUS: deployed
  REVISION: 1
  TEST SUITE: None
  NOTES:
  The Milvus server can be accessed via port 19530 on the following DNS name from within your cluster:
  my-release-milvus.milvus.svc.cluster.local

  Get the Milvus server URL by running these commands in the same shell:
    export POD_NAME=$(kubectl get pods --namespace milvus -l "app.kubernetes.io/name=milvus,app.kubernetes.io/instance=my-release,component=mishards" -o jsonpath="{.items[0].metadata.name}")
    kubectl --namespace milvus port-forward $POD_NAME 19530 19121

  For more information on running Milvus, visit:
  https://milvus.io/

$ kubectl get pod -n milvus
  NAME                                                 READY   STATUS     RESTARTS   AGE
  my-release-milvus-mishards-7cb6574bb5-jrcf4          0/1     Init:0/1   0          6m23s
  my-release-milvus-readonly-8588bdd49-7wtwt           0/1     Pending    0          6m23s
  my-release-milvus-writable-6db7bfc647-qrd69          0/1     Pending    0          6m23s
  my-release-mysql-5f69d5bd87-99zd5                    0/1     Pending    0          6m23s
  nfs-client-nfs-client-provisioner-7685d96cbc-wxfkb   1/1     Running    0          21m

As you can see pod stuck and can not running. Did anyone deploy Milvus on kubernetes cluster on-premise. Please help me!!!

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

oО清风挽发oО 2025-01-18 14:13:23

需要检查的是您是否有自定义 kubernetes 集群域。 Milvus 使用默认的 kubernetes 集群域 cluster.local 进行硬编码。这样做的问题是,它会破坏服务发现,因为 etcd 节点无法找到彼此。

Something to check is if you have a custom kubernetes cluster domain. Milvus is hard coded with the default kubernetes cluster domain of cluster.local. The problem with this is that it breaks service discovery as the etcd nodes can't find each other.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文