how can i set authenticated access the milvusdb deployment by milvus-operator

[hxlsky]

i have deployment the milvus in k8s by milvus-operator,how can i set the user and passwd access the milvusdb?

[hxlsky]

[hxlsky]

my yaml file as flowing show:

`# This sample is used to deploy milvus with external dependencies

change the to match your environment

apiVersion: milvus.io/v1beta1
kind: Milvus
metadata:
name: milvus-dev
namespace: middleware
labels:
app: milvus
spec:
mode: cluster
components:
enableRollingUpdate: true
imageUpdateMode: rollingUpgrade
proxy:
replicas: 1
dataNode:
replicas: 1
indexNode:
replicas: 1
queryNode:
replicas: 1
mixCoord:
replicas: 1
image: registry.cn-shenzhen.aliyuncs.com/ask8s/milvus:v2.4.15
imagePullPolicy: IfNotPresent
resources:
limits:
cpu: '2'
memory: 4Gi
requests:
cpu: '0.1'
memory: 128Mi
config:
etcd:
rootPath: milvus-dev
#auth:
# enabled: true
# userName: milvus
# password: milvus
msgChannel:
chanNamePrefix:
cluster: milvus-dev
minio:
bucketName: milvus-dev
# config the prefix of the bucket milvus will use
rootPath: milvus/milvus-dev
kafka:
# securityProtocol supports: PLAINTEXT, SSL, SASL_PLAINTEXT, SASL_SSL
securityProtocol: PLAINTEXT
# saslMechanisms supports: PLAIN, SCRAM-SHA-256, SCRAM-SHA-512
saslMechanisms: PLAIN
saslUsername: ""
saslPassword: ""
dependencies:
etcd:
external: true
endpoints: ["192.168.1.106:2379"]
storage:
external: true
endpoint: "192.168.1.106:9000"
secretRef: "milvus-s3-secret"
# if you want to use s3 check ./milvus_s3.yaml
type: MinIO
msgStreamType: "kafka"
kafka:
external: true
brokerList:
- "192.168.1.106:9092"`

[yhmo]

Set spec.common.security.authorizationEnabled to true to enable authentication.
https://milvus.io/docs/authenticate.md?tab=operator

spec:
  # Omit other fields ...
  config:
    common:
      security:
        authorizationEnabled: true

cert-manager is not for "milvus authentication"

[hxlsky]

hi,it is take no effect
the root is default passwd is Milvus,but i input othere passwd such as 123456,it can login in also,why?

[hxlsky]

it edit the yaml file(milvus_cluster_external_dependencies.yaml) and then do the flowing command:
[root@master my_yaml]# kubectl apply -f milvus_cluster_external_dependencies.yaml
milvus.milvus.io/milvus-dev configured

[hxlsky]

[hxlsky]

it seems take some minutes, it can take effect,why?
no immediately

[LoveEachDay]

yes

[hxlsky]

hi, if i edit the yaml file,change
from
image: milvusdb/milvus:v2.4.15
to
image: milvusdb/milvus:v2.4.17

and then apply the config file
what happen?

[LoveEachDay]

Same as change milvus config, it will trigger a milvus component rollout one by one.

[hxlsky]

it will upgrade the milvusdb from v2.4.15 to v2.4.17?

[LoveEachDay]

yes