milvus: [Bug]: Client sent an HTTP request to an HTTPS server.

Is there an existing issue for this?

I have searched the existing issues

Environment

- Milvus version:
- Deployment mode(standalone or cluster): standalone 2.3.1
- MQ type(rocksmq, pulsar or kafka):    
- SDK version(e.g. pymilvus v2.0.0rc2): 
- OS(Ubuntu or CentOS): CentOS
- CPU/Memory: 
- GPU: 
- Others:

Current Behavior

With Milvus-operator, deploy milvus single-node mode, but rely on Etcd and minio external clusters.

Expected Behavior

milvus standalone should be running.

Steps To Reproduce

1. vim milvs-external.yaml
2. kubectl apply -f milvs-external.yaml
3. kubectl describe milvus >desc.txt
4.kubectl logs hll-release-milvus-standalone-d57df84d8-qdmms > log.txt

### Milvus Log

[milvs-external.txt](https://github.com/milvus-io/milvus/files/13213385/milvs-external.txt)
[desc.txt](https://github.com/milvus-io/milvus/files/13213398/desc.txt)
[log.txt](https://github.com/milvus-io/milvus/files/13213393/log.txt)



### Anything else?

About this issue

Original URL
State: closed
Created 8 months ago
Comments: 36 (17 by maintainers)

Most upvoted comments

Or you can just delete the k8s service minio and rename it to other name than just minio, like minio-service or so

Sry for the delay, thank u @haorenfsa After I move minio to a different namespace in k8s, milvus is worked. but idk why it work ,hh

gaoyuan5251 on Nov 9, 2023

milvus.yaml.txt

@haorenfsa done

gaoyuan5251 on Nov 7, 2023

Or you can just delete the k8s service minio and rename it to other name than just minio, like minio-service or so

haorenfsa on Nov 7, 2023