milvus-io/milvus
GitHub で見る[Feat]: Milvus cannot connect to kafka&minio with ssl
Open
#27,461 opened on 2023年10月2日
help wantedkind/feature
説明
Is there an existing issue for this?
- I have searched the existing issues
Environment
- Milvus version: latest
- Deployment mode(standalone or cluster): standalone
- MQ type(rocksmq, pulsar or kafka): kafka with ssl
- Metadata storage: etcd with ssl
- S3: minio with ssl
Current Behavior
milvus cannot connect external services kafka & minio which configued with ssl
Expected Behavior
milvus could connect kafka & minio with ssl
Steps To Reproduce
1. Startup external services etcd, minio and kafka with ssl
2. Configure milvus
.yaml
etcd:
endpoints: [external-etcd-address]
......
ssl:
enabled: false # Whether to support ETCD secure connection mode
tlsCert: /path/to/etcd-client.pem # path to your cert file
tlsKey: /path/to/etcd-client-key.pem # path to your key file
tlsCACert: /path/to/ca.pem # path to your CACert file
# TLS min version
# Optional values: 1.0, 1.1, 1.2, 1.3。
# We recommend using version 1.2 and above
tlsMinVersion: 1.3
......
......
minio:
address: external-minio-address
......
useSSL: true
......
......
kafka:
brokerList: [external-kafka-brokers-address]
......
securityProtocol: SSL
......
......
3. startup milvus, cannot connect to kafka & minio, ssl handshake will fail
Milvus Log
No response
Anything else?
should handle kafka & minio ssl just like etcd