When debugging it turns out that you may need more information.
The "export-milvus-log.sh" script will export logs of milvus cluster for further discovery:
https://github.com/milvus-io/milvus/tree/master/deployments/export-log
Once you have the full logs you can spot things that can happen on initial configuration, like not properly setting up minio.
When you see something like this either DNS, networking or configuration file is pointing to wrong place.
Make sure you test that minio and etcd are running normally and accessible.
dial tcp: lookup my-release-minio on 10.104.64.10:53: no such host"]
If you are not using cloud object storage, make sureto set up a default storageclass for block storage for your kubernetes cluster.