shaoyue

Oh, I know what's going on. You're using the private certificate signed by yourself. So you need to add the `server.pem` when connecting. Try this: `connections.connect("default", host="k8s-milvus.example.com", port="443", secure=True, server_pem_path="/home/testuser/milvus/cert/server.pem")`

> Want to note, that ingress tls certs are generated by gen.sh and i try connect with them *.pem. But in user.yaml using defaults certs generating by milvus before start...

alter a bit: `connections.connect("default", host="milvus.example.com", port="443", secure=True, server_pem_path="/home/testuser/milvus/ca.pem", server_name="milvus.example.com")`

@XuanYang-cn These configurations are indeed very confusing.... For now `server_pem_path` is not working without `server_name`. This seems to be a bug.

https://github.com/milvus-io/pymilvus/issues/1962

Oh, good catch! The server_name thing is indeed a bug to me. We'll fix it soon. Happy hacking with Milvus!

So extra guide should be added using minikube. Most people don't have a real k8s-cluster to play with.

fixed in https://github.com/milvus-io/pymilvus/issues/1962

Hi @indyvanmol , please check if `milvus.mysite.be` is correctly resolved to the ip of nginx ingress. And try `curl --http2 https://milvus.mysite.be/` to see if there's any clues from the output

@indyvanmol that means the ingress is not created correctly. what's the output of `kubectl describe ingress`?