Same deployment in k8s's different environments, test work and stage error.

[weihaopeng]

Hi, we deploy milvus with the method offline helm in our k8s. We use same deployment in different environments. The test environment is success, while stage environment get some errors.

Here is our deploy steps:

# download deploy template
wget https://raw.githubusercontent.com/milvus-io/milvus-helm/master/charts/milvus/values.yaml
 
# modify deploy template
vi values.yaml
# generate k8s deploy template
helm template -f values.yaml my-release --namespace  meta --set cluster.enabled=false --set etcd.replicaCount=1 --set minio.mode=standalone --set pulsar.enabled=false milvus/milvus > milvus_manifest.yaml
 
# download required images
wget https://raw.githubusercontent.com/milvus-io/milvus/master/deployments/offline/requirements.txt
wget https://raw.githubusercontent.com/milvus-io/milvus/master/deployments/offline/save_image.py
 
# push images to baidubce
docker push registry.baidubce.com/devops-public/milvus-config-tool:v0.1.1
docker push registry.baidubce.com/devops-public/milvus:v2.2.8
docker push registry.baidubce.com/devops-public/minio:RELEASE.2023-03-20T20-16-18Z
docker push registry.baidubce.com/devops-public/milvusdb-etcd:3.5.5-r2
 
# deploy to specific namespace
kubectl apply -f milvus_manifest.yaml -n meta

The error log:

standalone.log

The most errors are:

1. find no available rootcoord, check rootcoord state
2. etcdserver: requested lease not found

And we found the mino server, etcd cluster are no problems both in test environment and stage environment.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. Rotten issues close after 30d of inactivity. Close the stale issues and pull requests after 7 days of inactivity. Reopen the issue with /reopen.