Monitor the cluster status until it transitions to the Running state:

kubectl get cluster milvus-cluster -n demo -w

Expected Output:

NAME                CLUSTER-DEFINITION   TERMINATION-POLICY   STATUS     AGE
milvus-standalone   milvus               Delete               Creating   40s
milvus-standalone   milvus               Delete               Creating   71s
milvus-standalone   milvus               Delete               Creating   71s
milvus-standalone   milvus               Delete               Updating   71s
milvus-standalone   milvus               Delete               Running    2m55s

Check the component and pod status:

kubectl get component -n demo -l app.kubernetes.io/instance=milvus-standalone

Expected Output:

NAME                       DEFINITION                        SERVICE-VERSION   STATUS    AGE
milvus-standalone-etcd     etcd-3-1.0.0                      3.5.15            Running   3m5s
milvus-standalone-milvus   milvus-standalone-1.0.0           v2.3.2            Running   114s
milvus-standalone-minio    milvus-minio-1.0.0                8.0.17            Running   3m5s

kubectl get pods -l app.kubernetes.io/instance=milvus-standalone -n demo

Expected Output:

NAME                         READY   STATUS    RESTARTS   AGE
milvus-standalone-etcd-0     2/2     Running   0          4m31s
milvus-standalone-milvus-0   1/1     Running   0          3m20s
milvus-standalone-minio-0    1/1     Running   0          4m31s

Once the cluster status becomes Running, your Milvus cluster is ready for use.