Is your feature request related to a problem? Please describe.
Today when creating a milvus cluster using the milvus-operator, it spins up an ETCD cluster which is not possible to use already existing persistent volume claims. This makes it impossible to recover from certain crashes/failures, and requires the collection-data to be wiped and reimported.
For this reason an externally controlled ETCD cluster could be used, but then the milvus-operator does not support for auth when connecting to external dependencies.
Describe the solution you'd like.
I'd like to be able to set auth for all of the available external dependencies
Describe an alternate solution.
Allowing the specify already existing PVCs for e.g. ETCD when creating the Milvus cluster
Is there an existing issue for this?
Is your feature request related to a problem? Please describe.
Today when creating a milvus cluster using the milvus-operator, it spins up an ETCD cluster which is not possible to use already existing persistent volume claims. This makes it impossible to recover from certain crashes/failures, and requires the collection-data to be wiped and reimported.
For this reason an externally controlled ETCD cluster could be used, but then the milvus-operator does not support for auth when connecting to external dependencies.
Describe the solution you'd like.
I'd like to be able to set auth for all of the available external dependencies
Describe an alternate solution.
Allowing the specify already existing PVCs for e.g. ETCD when creating the Milvus cluster
Anything else? (Additional Context)
No response