Fix NATS configuration guide as per CRD

[kailash360]

Fixes #1072

This pull request fixes the NATS configuration guide for Milvus Operator.

Existing Behaviour

There is mistmatch between the CRD schema for NATS and the manifest given in the document guide. This causes error while starting milvus with the current guide.

New Behaviour

The manifest documentation for NATS configuration is now matching the CRD. The existing fields are now placed under spec.config.natsmq which allows to inject additional fields.

[chyezh]

thx for your debugging of docs,
milvus has been removed the support of nats since 2.6, I will provide a PR to remove these document from repository.

[kailash360]

Thanks for the update @chyezh. But I am currently using Milvus version 2.6.x and it seems that it is able to take up NATS config using just msgStreamType: natsmq and spin up locally.

So, has the removal of NATS not been completed yet? If not, by when do we plan to completely let go of NATS from Milvus? Also, I will appreciate if you can throw some light on why we are removing NATS.

[chyezh]

Thanks for the update @chyezh. But I am currently using Milvus version 2.6.x and it seems that it is able to take up NATS config using just msgStreamType: natsmq and spin up locally.

So, has the removal of NATS not been completed yet? If not, by when do we plan to completely let go of NATS from Milvus? Also, I will appreciate if you can throw some light on why we are removing NATS.

It has been removed indeed, maybe the configuration didn't take effect on your cluster.
You can check the label wal_name of milvus streamingnode metric milvus_wal_info to confirm to confirm which mq your cluster used.

[chyezh]

removed by
milvus-io/milvus-docs#3439
milvus-io/milvus-docs#3440