To support access to milvus via ingress which take https:443 as the middle layer.

[congguosn]

Describe the feature:
Currently, attu does not support access milvus if k8s ingress is deployed as a load balancer, for attu hardcodes ssl to false which will cause error like below.

Error: 13 INTERNAL: Received RST_STREAM with code 2 triggered by internal client error: Protocol error

Describe a specific use case for the feature:
If we use aws ingress as load balancer to distribute GRPC traffic, HTTPS will be treated as the access layer and 443 is used for listening the traffic. But attu could not support it as the reason (ssl setting) described above.

[congguosn]

file path: server/src/milvus/milvus.service.ts
function name: async connectMilvus

[shanghaikid]

@haorenfsa can you help for this? I am not the expert of networking.

[shanghaikid]

by the way, what do you mean hardcodes ssl to false? and what's the version of your attu?

[congguosn]

Hi @shanghaikid, my attu version is v2.3.8. There is a parameter passed to MilvusClient constructor named clientOptions, in which ssl could be set to false or true, but current version does not customize it and just use the default value(false).

// create the client const milvusClient: MilvusClient = new MilvusClient(clientOptions);

[shanghaikid]

Hi @shanghaikid, my attu version is v2.3.8. There is a parameter passed to MilvusClient constructor named clientOptions, in which ssl could be set to false or true, but current version does not customize it and just use the default value(false).

// create the client const milvusClient: MilvusClient = new MilvusClient(clientOptions);

I think it depends on the address right now, if it starts with https. ok I will add an option.

[shanghaikid]

Hi @shanghaikid, my attu version is v2.3.8. There is a parameter passed to MilvusClient constructor named clientOptions, in which ssl could be set to false or true, but current version does not customize it and just use the default value(false).

// create the client const milvusClient: MilvusClient = new MilvusClient(clientOptions);

I've read the node sdk code. in your case, I guess you add the ROOT_CERT_PATH env is enough, it will create the grpc credentials.

https://github.com/milvus-io/milvus-sdk-node/blob/a4bfa9761871a1ce0af83b319dbc48c2dd8d9eb3/milvus/grpc/BaseClient.ts#L172

Here is the basic tested docker command, you can add these env to your k8s yaml.
docker run -p 8000:3000
-v /your-tls-file-path:/app/tls
-e ATTU_LOG_LEVEL=info
-e ROOT_CERT_PATH=/app/tls/ca.pem
-e PRIVATE_KEY_PATH=/app/tls/client.key
-e CERT_CHAIN_PATH=/app/tls/client.pem
-e SERVER_NAME=your_server_name
zilliz/attu:dev

[congguosn]

Thank you! Will try it.