Configuration Management Refine: We have removed the configuration merge before startup. Now, we will maintain three separate config files: user.yaml, default.yaml, and milvus.yaml. The user.yaml file can specify custom configurations and has the highest precedence. The default.yaml file specifies all dependencies configurations, which are automatically injected by the Helm chart. The milvus.yaml file is the default configuration, minted from the image.
Pulsar Upgrade: We have upgraded the Pulsar version from 2.8.2 to 2.9.5.
Milvus Upgrade: We have bumped the Milvus version from 2.4.5 to 2.4.6.
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]
[ x] Chart Version bumped
[ x] Variables are documented in the README.md
[ ] Title of the PR starts with chart name (e.g. [mychartname])
Needs approval from an approver in each of these files:
- ~~[OWNERS](https://github.com/zilliztech/milvus-helm/blob/master/OWNERS)~~ [LoveEachDay]
Approvers can indicate their approval by writing `/approve` in a comment
Approvers can cancel approval by writing `/approve cancel` in a comment
What this PR does / why we need it:
user.yaml
,default.yaml
, andmilvus.yaml
. Theuser.yaml
file can specify custom configurations and has the highest precedence. Thedefault.yaml
file specifies all dependencies configurations, which are automatically injected by the Helm chart. Themilvus.yaml
file is the default configuration, minted from the image.Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]
[mychartname]
)