Creating a Milvus Database
This page covers the configuration specific to Milvus — its Database Mode and any engine-specific settings shown below. The rest of the creation flow — opening the wizard, namespace and name, version, machine profile, storage, and optional features — is the same for every engine and is documented in Common Steps.
Database Mode
Select the topology under Database Mode:
- Standalone — A single-node Milvus instance.
- Distributed — A multi-node Milvus deployment with separated components for scale and availability.
| Field | Description |
|---|---|
| Number of Replicas | Number of nodes/components in the distributed deployment. Required for Distributed. |
Milvus Dependencies & Settings
Milvus depends on a metadata store (etcd) and object storage, and exposes a few instance-level toggles.
Meta Storage (etcd)
| Field | Description |
|---|---|
| Externally Managed | Toggle on to use an existing etcd instead of provisioning one. |
| Endpoints | etcd endpoints to connect to when externally managed. |
| Size | Number of etcd nodes when provisioned by the platform. |
Object Storage
| Field | Description |
|---|---|
| Config Secret Name | Secret holding the object storage (e.g. S3/MinIO) configuration. |
Other Settings
| Field | Description |
|---|---|
| Disable Security | Run without authentication (development only). |
| Halted | Create the instance in a halted (stopped) state. |
| Configuration Secret / Inline | Provide engine configuration via a referenced Secret or inline key-value pairs. |
Create a Milvus Database
- Open the wizard and select Milvus — see Getting Started and Select a Database Type.
- Set the namespace and name.
- Pick the database version and the Database Mode described above, then set the machine profile and storage — see Configure the Database.
- Optionally configure Advanced Configuration (labels, deletion policy, credentials, point-in-time recovery) and Additional Options (monitoring, backup, TLS, gateway).
- Click Deploy.