k8s集群部署采用最低配置时出现问题 #30599
Replies: 4 comments 6 replies
-
|
seems like you got a typo |
Beta Was this translation helpful? Give feedback.
-
|
I don't think he got a typo, the yaml file name starts with "milvus", not "mmilvus" |
Beta Was this translation helpful? Give feedback.
-
|
Hello @xiaofan-luan I got the same error today, but I didn't type anything, strictly followed this official document: https://milvus.io/docs/install_cluster-milvusoperator.md The operator is running $ oc get pods -n milvus-operator
NAME READY STATUS RESTARTS AGE
milvus-operator-checker-4nf6l 1/1 Running 0 43s
# and then
$ oc apply -f https://raw.githubusercontent.com/zilliztech/milvus-operator/main/config/samples/milvus_cluster_default.yaml
Error from server (InternalError): error when creating milvus_cluster_default.yaml:
Internal error occurred: failed calling webhook "mmilvus.kb.io":
failed to call webhook:
Post "https://milvus-operator-webhook-service.milvus-operator.svc:443/mutate-milvus-io-v1beta1-milvus?timeout=10s":
no endpoints available for service "milvus-operator-webhook-service"Any special configuration do we need? |
Beta Was this translation helpful? Give feedback.
-
|
could you tall me , please? |
Beta Was this translation helpful? Give feedback.
-
|
切换成了 helm. 有一个 pod 启动不了 日志如下 是缺少什么步骤吗? |
Beta Was this translation helpful? Give feedback.
-
|
[2024/06/14 08:14:15.848 +00:00] [INFO] [etcd/etcd_util.go:49] ["create etcd client"] [useEmbedEtcd=false] [useSSL=false] [endpoints="[my-milvus-etcd:2379]"] [minVersion=1.3] The datacoord could not connect to etcd by the endpoint "my-milvus-etcd:2379". |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for your reply, I see from the document there should be pod named I don't know why the etcd pod is not created. I think that's why milvus cannot connect to it. |
Beta Was this translation helpful? Give feedback.
-
|
Yes, by helm deployment, there are should be my-release-etcd-0/my-release-etcd-1/my-release-etcd-2 running. "Check Milvus cluster status" is mentioned in this doc: https://milvus.io/docs/install_cluster-helm.md |
Beta Was this translation helpful? Give feedback.
-
|
The $ oc get po
NAME READY STATUS RESTARTS AGE
my-milvus-minio-b94d9974-9z8k6 1/1 Running 0 2m20s
my-milvus-standalone-7d97c86f9b-c9fhr 0/1 CrashLoopBackOff 3 (26s ago) 2m21s
$ oc get sts
NAME READY AGE
my-milvus-etcd 0/1 12m
$ oc describe sts my-milvus-etcd
create Pod my-milvus-etcd-0 in StatefulSet my-milvus-etcd failed error:
pods "my-milvus-etcd-0" is forbidden: unable to validate against any security context constraint:
[provider "anyuid": Forbidden: not usable by user or serviceaccount,
provider "pipelines-scc": Forbidden: not usable by user or serviceaccount,
provider "my-milvus-minio": Forbidden: not usable by user or serviceaccount,
provider restricted-v2: .spec.securityContext.fsGroup:
Invalid value: []int64{1001}: 1001 is not an allowed group,
provider restricted-v2: .containers[0].runAsUser:
Invalid value: 1001: must be in the ranges: [1000770000, 1000779999], |
Beta Was this translation helpful? Give feedback.
-
|
Hi. I fixed the issue via Hope that when installing helm chart, we can do something like this: helm install my-milvus milvus/milvus --set etcd.podSecurityContext.enabled=false --set etcd.containerSecurityContext.enabled=false |
Beta Was this translation helpful? Give feedback.
-
Error from server (InternalError): error when creating "milvus_cluster_minimum.yaml": Internal error occurred: failed calling webhook "mmilvus.kb.io": Post "https://milvus-operator-webhook-service.milvus-operator.svc:443/mutate-milvus-io-v1beta1-milvus?timeout=10s": context deadline exceeded
Beta Was this translation helpful? Give feedback.
All reactions