[Feature]: milvus merge config with custom config

[locustbaby]

Is there an existing issue for this?

• I have searched the existing issues

Is your feature request related to a problem? Please describe.

#22516
There are some tools inside of milvus' pod help milvus merge user's config into milvus.yaml, such as /milvus/tools/run-helm.sh,/milvus/tools/merge, but as default, merge will write the milvus.yaml which belong to user root, when milvus run as a non-root user, merge will fail.

Describe the solution you'd like.

I don't think the merge is necessary, most open-source projects will merge the user's config automatically, such as kubectl, helm, nginx and so on.
Wish milvus can accept the user's yaml and merge automatically and better don't add more options for forward compatibility

Describe an alternate solution.

No response

Anything else? (Additional Context)

No response

[locustbaby]

@jiaoew1991

[jiaoew1991]

support read user. yaml, default.yaml, milvus.yaml as this order.

[xiaofan-luan]

/assign @smellthemoon

[arunkumara8]

@locustbaby Is there a fix or workaround for this issue?

[xiaofan-luan]

I believe @smellthemoon is working on that.
Let's fix it on 2.3.x

[smellthemoon]

working on it now.

[smellthemoon]

init container will read user. yaml, default.yaml, milvus.yaml and then write milvus.yaml, which may cause permission denied(write need root permissions). now #22583 support to multi yaml files. But init container has not removed now, so container still need root permissions.
two solution.

1. remove init container. Test locally, it can not merge multi yaml files in master and v2.3. Discussed with @locustbaby , seems it has some bugs when upgrade. I will support the feature and try to reproduce it.
2. change the document permission level. Considering the security issues, I am not very inclined to this method。

All in all, I will choose the first method to solve this problem at this stage and will update if there is any progress.