GenkenWei
GenkenWei
@LoveEachDay could you review this PR?
@xiaofan-luan could you review this PR?
https://github.com/zilliztech/attu/blob/main/Dockerfile#L22 https://github.com/milvus-io/bitnami-docker-etcd/blob/3.5.0-new/3.5/debian-11/Dockerfile#L1 what about here?
@LoveEachDay Change to latest version [focal-20240427](https://hub.docker.com/layers/library/ubuntu/focal-20240427/images/sha256-cc9cc8169c9517ae035cf293b15f06922cb8c6c864d625a72b7b18667f264b70?context=explore) now, please review, thanks.
/assign @yanliang567
It may caused by the this invalidated seetings. ``` extraConfigFiles: user.yaml: | common: security: authorizationEnabled: true chanNamePrefix: cluster: test1 ``` Actual: [channel=by-dev-rootcoord-dml_1_452146874032006318v0] Expect: [channel=test1-rootcoord-dml_1_452146874032006318v0] Please provide a workaround for upgrade...
``` extraConfigFiles: user.yaml: | common: security: authorizationEnabled: true msgChannel: chanNamePrefix: cluster: test1 ``` or ``` extraConfigFiles: user.yaml: | common: security: authorizationEnabled: true msgChannel: chanNamePrefix: cluster: test1 ``` ????
The value does not work in milvus-helm-value.yaml from Milvus 2.4.8 to 2.4.9. ``` extraConfigFiles: user.yaml: | common: security: authorizationEnabled: true chanNamePrefix: cluster: test1 ``` It works on Milvus 2.4.9 after...