Open anhnch30820 opened 3 months ago
@anhnch30820 For now it's supported in milvus-operator , we'll migrate it to helm soon.
https://github.com/zilliztech/milvus-operator/releases/tag/v0.9.15
thank you
Hi @haorenfsa, Does helm support dynamic for now?
@anhnch30820 No, I haven't got time to manage that. l list the changes needed below., so that you may change your deployment for dynamic config. Or if you're interested, you could also make a patch for our chart.
Each deploy should be added with:
/milvus/tools/run.sh
and related volumeMounts.initContainer
to copy binaries needed for run.sh
apiVersion: apps/v1
kind: Deployment
metadata:
name: milvus-indexnode
spec:
template:
spec:
containers:
- args:
- /milvus/tools/run.sh
- milvus
- run
- indexnode
name: indexnode
volumeMounts:
- mountPath: /milvus/configs/operator
name: milvus-config
readOnly: true
- mountPath: /milvus/tools
name: tools
initContainers:
- args:
- /init.sh
command:
- /bin/sh
image: milvusdb/milvus-tools:v1.0.0
resources: {}
volumeMounts:
- mountPath: /milvus/configs/operator
name: milvus-config
readOnly: true
- mountPath: /milvus/tools
name: tools
volumes:
- configMap:
name: milvus
name: milvus-config
- emptyDir: {}
name: tools
I see document in K8s A container using a ConfigMap as a subPath volume mount will not receive ConfigMap updates. And helm use subPath: