Mengonfigurasi dan menyebarkan kluster Valkey di Azure Kubernetes Service (AKS)

Dalam artikel ini, kami mengonfigurasi dan menyebarkan kluster Valkey di Azure Kubernetes Service (AKS), termasuk pembuatan kluster Valkey ConfigMap, pod kluster primer dan replika untuk memastikan redundansi dan replikasi zona, dan Anggaran Gangguan Pod (PDB) untuk memastikan ketersediaan tinggi.

Catatan

Artikel ini berisi referensi ke istilah master (utama) dan budak (replika), yang merupakan istilah yang tidak lagi digunakan Microsoft. Ketika istilah dihapus dari perangkat lunak Valkey, kami akan menghapusnya dari artikel ini.

Menyambungkan ke kluster AKS

Catatan

Jika Anda menggunakan Terraform, pastikan Anda mengganti placeholder dalam kode dengan output aktual dari komando Terraform saat penyebaran infrastruktur.

  • Konfigurasikan kubectl untuk menyambungkan ke kluster AKS Anda menggunakan perintah az aks get-credentials.

    az aks get-credentials --resource-group $MY_RESOURCE_GROUP_NAME --name $MY_CLUSTER_NAME --overwrite-existing --output table

Membuat namespace

  • Buat namespace layanan untuk kluster Valkey menggunakan kubectl create namespace perintah .

    kubectl create namespace valkey --dry-run=client --output yaml | kubectl apply -f -

    Contoh output:

    namespace/valkey created

Membuat rahasia

  1. Buat kata sandi acak untuk kluster Valkey menggunakan openssl dan simpan di brankas kunci Azure Anda menggunakan az keyvault secret set perintah .

    export SECRET=$(openssl rand -base64 32)
echo requirepass $SECRET > /tmp/valkey-password-file.conf
echo primaryauth $SECRET >> /tmp/valkey-password-file.conf
az keyvault secret set --vault-name $MY_KEYVAULT_NAME --name valkey-password-file --file /tmp/valkey-password-file.conf --output none
rm /tmp/valkey-password-file.conf

  2. Atur kebijakan untuk mengizinkan identitas yang ditetapkan pengguna mendapatkan rahasia menggunakan az keyvault set-policy perintah .

    az keyvault set-policy --name $MY_KEYVAULT_NAME --object-id $userAssignedObjectID --secret-permissions get --output table

Mendapatkan detail identitas yang ditetapkan pengguna

  • Dapatkan ID identitas dan ID objek yang dibuat oleh tambahan Penyedia Rahasia Azure Key Vault menggunakan perintah az aks show.

    export userAssignedIdentityID=$(az aks show --resource-group $MY_RESOURCE_GROUP_NAME --name $MY_CLUSTER_NAME --query addonProfiles.azureKeyvaultSecretsProvider.identity.clientId --output tsv)
export userAssignedObjectID=$(az aks show --resource-group $MY_RESOURCE_GROUP_NAME --name $MY_CLUSTER_NAME --query addonProfiles.azureKeyvaultSecretsProvider.identity.objectId --output tsv)

Mengonfigurasi akses ke kata sandi Valkey yang disimpan di Azure Key Vault

  • Buat SecretProviderClass sumber daya untuk mengakses kata sandi Valkey yang disimpan di brankas kunci Anda menggunakan kubectl apply perintah .

    export TENANT_ID=$(az account show --query tenantId --output tsv)
kubectl apply -f - <<EOF
---
apiVersion: secrets-store.csi.x-k8s.io/v1
kind: SecretProviderClass
metadata:
  name: valkey-password
  namespace: valkey
spec:
  provider: azure
  parameters:
    usePodIdentity: "false"
    useVMManagedIdentity: "true"
    userAssignedIdentityID: "${userAssignedIdentityID}"
    keyvaultName: ${MY_KEYVAULT_NAME}              # the name of the AKV instance
    objects: |
      array:
        - |
          objectName: valkey-password-file
          objectAlias: valkey-password-file.conf
          objectType: secret
    tenantId: "${TENANT_ID}" # the tenant ID of the AKV instance
EOF

Membuat file konfigurasi Valkey

  • Buat ConfigMap sumber daya untuk menyimpan file konfigurasi Valkey.

    kubectl apply -f - <<EOF
apiVersion: v1
kind: ConfigMap
metadata:
  name: valkey-cluster
  namespace: valkey
data:
  valkey.conf:  |+
    cluster-enabled yes
    cluster-node-timeout 15000
    cluster-config-file /data/nodes.conf
    appendonly yes
    protected-mode yes
    dir /data
    port 6379
    include /etc/valkey-password/valkey-password-file.conf
EOF

    Contoh output:

    configmap/valkey-cluster created

Membuat pod utama kluster Valkey

  • Buat StatefulSet sumber daya dengan spec.affinity tujuan adalah untuk menjaga semua utama di zona 1 dan zona 2, sebaiknya di simpul yang berbeda, menggunakan kubectl apply perintah .

    kubectl apply -f - <<EOF
---
apiVersion: apps/v1
kind: StatefulSet
metadata:
  name: valkey-masters
  namespace: valkey
spec:
  serviceName: "valkey-masters"
  replicas: 3
  selector:
    matchLabels:
      app: valkey
  template:
    metadata:
      labels:
        app: valkey
        appCluster: valkey-masters
    spec:
      terminationGracePeriodSeconds: 20
      affinity:
        nodeAffinity:
          requiredDuringSchedulingIgnoredDuringExecution:
            nodeSelectorTerms:
            - matchExpressions:
              - key: agentpool
                operator: In
                values:
                - valkey
              - key: topology.kubernetes.io/zone
                operator: In
                values:
                - ${MY_LOCATION}-1
            - matchExpressions:
              - key: agentpool
                operator: In
                values:
                - valkey
              - key: topology.kubernetes.io/zone
                operator: In
                values:
                - ${MY_LOCATION}-2
        podAntiAffinity:
          preferredDuringSchedulingIgnoredDuringExecution:
          - weight: 100
            podAffinityTerm:
              labelSelector:
                matchExpressions:
                - key: app
                  operator: In
                  values:
                  - valkey
              topologyKey: topology.kubernetes.io/zone
          - weight: 90
            podAffinityTerm:
              labelSelector:
                matchExpressions:
                - key: app
                  operator: In
                  values:
                  - valkey
              topologyKey: kubernetes.io/hostname
      containers:
      - name: role-master-checker
        image: "${MY_ACR_REGISTRY}.azurecr.io/valkey:latest"
        command:
          - "/bin/bash"
          - "-c"
        args:
          [
            "while true; do role=\$(valkey-cli --pass \$(cat /etc/valkey-password/valkey-password-file.conf | awk '{print \$2; exit}') role | awk '{print \$1; exit}');     if [ \"\$role\" = \"slave\" ]; then valkey-cli --pass \$(cat /etc/valkey-password/valkey-password-file.conf | awk '{print \$2; exit}') cluster failover; fi; sleep 30; done"
          ]
        volumeMounts:
        - name: valkey-password
          mountPath: /etc/valkey-password
          readOnly: true
      - name: valkey
        image: "${MY_ACR_REGISTRY}.azurecr.io/valkey:latest"
        env:
        - name: VALKEY_PASSWORD_FILE
          value: "/etc/valkey-password/valkey-password-file.conf"
        - name: MY_POD_IP
          valueFrom:
            fieldRef:
              fieldPath: status.podIP
        command:
          - "valkey-server"
        args:
          - "/conf/valkey.conf"
          - "--cluster-announce-ip"
          - "\$(MY_POD_IP)"
        resources:
          requests:
            cpu: "100m"
            memory: "100Mi"
        ports:
            - name: valkey
              containerPort: 6379
              protocol: "TCP"
            - name: cluster
              containerPort: 16379
              protocol: "TCP"
        volumeMounts:
        - name: conf
          mountPath: /conf
          readOnly: false
        - name: data
          mountPath: /data
          readOnly: false
        - name: valkey-password
          mountPath: /etc/valkey-password
          readOnly: true
      volumes:
      - name: valkey-password
        csi:
          driver: secrets-store.csi.k8s.io
          readOnly: true
          volumeAttributes:
            secretProviderClass: valkey-password
      - name: conf
        configMap:
          name: valkey-cluster
          defaultMode: 0755
  volumeClaimTemplates:
  - metadata:
      name: data
    spec:
      accessModes: [ "ReadWriteOnce" ]
      storageClassName: managed-csi-premium
      resources:
        requests:
          storage: 20Gi
EOF

    Contoh output:

    statefulset.apps/valkey-masters created

Membuat pod kluster replika Valkey

  • Buat sumber daya kedua StatefulSet untuk replika Valkey dengan spec.affinity tujuan menjaga semua replika di zona 3, sebaiknya di simpul-simpul yang berbeda, menggunakan kubectl apply perintah.

    kubectl apply -f - <<EOF
---
apiVersion: apps/v1
kind: StatefulSet
metadata:
  name: valkey-replicas
  namespace: valkey
spec:
  serviceName: "valkey-replicas"
  replicas: 3
  selector:
    matchLabels:
      app: valkey
  template:
    metadata:
      labels:
        app: valkey
        appCluster: valkey-replicas
    spec:
      terminationGracePeriodSeconds: 20
      affinity:
        nodeAffinity:
          requiredDuringSchedulingIgnoredDuringExecution:
            nodeSelectorTerms:
            - matchExpressions:
              - key: agentpool
                operator: In
                values:
                - valkey
              - key: topology.kubernetes.io/zone
                operator: In
                values:
                - ${MY_LOCATION}-3
        podAntiAffinity:
          preferredDuringSchedulingIgnoredDuringExecution:
          - weight: 90
            podAffinityTerm:
              labelSelector:
                matchExpressions:
                - key: app
                  operator: In
                  values:
                  - valkey
              topologyKey: kubernetes.io/hostname
      containers:
      - name: valkey
        image: "${MY_ACR_REGISTRY}.azurecr.io/valkey:latest"
        env:
        - name: VALKEY_PASSWORD_FILE
          value: "/etc/valkey-password/valkey-password-file.conf"
        - name: MY_POD_IP
          valueFrom:
            fieldRef:
              fieldPath: status.podIP
        command:
          - "valkey-server"
        args:
          - "/conf/valkey.conf"
          - "--cluster-announce-ip"
          - "\$(MY_POD_IP)"
        resources:
          requests:
            cpu: "100m"
            memory: "100Mi"
        ports:
            - name: valkey
              containerPort: 6379
              protocol: "TCP"
            - name: cluster
              containerPort: 16379
              protocol: "TCP"
        volumeMounts:
        - name: conf
          mountPath: /conf
          readOnly: false
        - name: data
          mountPath: /data
          readOnly: false
        - name: valkey-password
          mountPath: /etc/valkey-password
          readOnly: true
      volumes:
      - name: valkey-password
        csi:
          driver: secrets-store.csi.k8s.io
          readOnly: true
          volumeAttributes:
            secretProviderClass: valkey-password
      - name: conf
        configMap:
          name: valkey-cluster
          defaultMode: 0755
  volumeClaimTemplates:
  - metadata:
      name: data
    spec:
      accessModes: [ "ReadWriteOnce" ]
      storageClassName: managed-csi-premium
      resources:
        requests:
          storage: 20Gi
EOF

    Contoh output:

    statefulset.apps/valkey-replicas created

Verifikasi distribusi pod dan node

  • Pastikan master-N dan replica-N berjalan di simpul dan zona yang terpisah dengan menggunakan perintah kubectl get nodes dan kubectl get pods.

    kubectl get pods -n valkey -o wide
kubectl get node -o custom-columns=Name:.metadata.name,Zone:".metadata.labels.topology\.kubernetes\.io/zone"

    Contoh output:

    NAME                READY   STATUS    RESTARTS   AGE     IP             NODE                             NOMINATED NODE   READINESS GATES
valkey-masters-0    1/1     Running   0          2m55s   10.224.0.4     aks-valkey-18693609-vmss000004   <none>           <none>
valkey-masters-1    1/1     Running   0          2m31s   10.224.0.137   aks-valkey-18693609-vmss000000   <none>           <none>
valkey-masters-2    1/1     Running   0          2m7s    10.224.0.222   aks-valkey-18693609-vmss000001   <none>           <none>
valkey-replicas-0   1/1     Running   0          88s     10.224.0.237   aks-valkey-18693609-vmss000005   <none>           <none>
valkey-replicas-1   1/1     Running   0          70s     10.224.0.18    aks-valkey-18693609-vmss000002   <none>           <none>
valkey-replicas-2   1/1     Running   0          48s     10.224.0.242   aks-valkey-18693609-vmss000005   <none>           <none>
Name                                Zone
aks-nodepool1-17621399-vmss000000   centralus-1
aks-nodepool1-17621399-vmss000001   centralus-2
aks-nodepool1-17621399-vmss000003   centralus-3
aks-valkey-18693609-vmss000000      centralus-1
aks-valkey-18693609-vmss000001      centralus-2
aks-valkey-18693609-vmss000002      centralus-3
aks-valkey-18693609-vmss000003      centralus-1
aks-valkey-18693609-vmss000004      centralus-2
aks-valkey-18693609-vmss000005      centralus-3

    Tunggu sekitar tiga menit hingga semua pod master-N dan pod replica-N berjalan sebelum melanjutkan ke langkah berikutnya.

Membuat layanan tanpa kepala

  • Buat tiga sumber daya headless Service (yang pertama untuk seluruh kluster, yang kedua untuk node primer, dan yang ketiga untuk node replika) yang digunakan untuk mendapatkan alamat IP pod Valkey menggunakan perintah kubectl apply.

    kubectl apply -f - <<EOF
apiVersion: v1
kind: Service
metadata:
  name: valkey-cluster
  namespace: valkey
spec:
  clusterIP: None
  ports:
  - name: valkey-port
    port: 6379
    protocol: TCP
    targetPort: 6379
  selector:
    app: valkey
  sessionAffinity: None
  type: ClusterIP
EOF

kubectl apply -f - <<EOF
apiVersion: v1
kind: Service
metadata:
  name: valkey-masters
  namespace: valkey
spec:
  clusterIP: None
  ports:
  - name: valkey-port
    port: 6379
    protocol: TCP
    targetPort: 6379
  selector:
    app: valkey
    appCluster: valkey-masters
  sessionAffinity: None
  type: ClusterIP
EOF

kubectl apply -f - <<EOF
apiVersion: v1
kind: Service
metadata:
  name: valkey-replicas
  namespace: valkey
spec:
  clusterIP: None
  ports:
  - name: valkey-port
    port: 6379
    protocol: TCP
    targetPort: 6379
  selector:
    app: valkey
    appCluster: valkey-replicas
  sessionAffinity: None
  type: ClusterIP
EOF

    Contoh output:

    service/valkey-cluster created
service/valkey-masters created
service/valkey-replicas created

Membuat Anggaran Gangguan Pod (PDB)

  • Buat Batas Gangguan Pod (PDB) untuk memastikan bahwa tidak lebih dari satu pod tidak aktif selama gangguan sukarela, seperti peningkatan atau pemeliharaan. Ini membantu menjaga stabilitas dan ketersediaan aplikasi Valkey dalam kluster Kubernetes.

    kubectl apply -f - <<EOF
apiVersion: policy/v1
kind: PodDisruptionBudget
metadata:
  name: valkey
  namespace: valkey
spec:
  maxUnavailable: 1
  selector:
    matchLabels:
      app: valkey
EOF

    Contoh output:

    poddisruptionbudget.policy/valkey created

Jalankan kluster Valkey

Dalam kluster Valkey, alokasi slot adalah bagian mendasar dari bagaimana data didistribusikan di seluruh simpul. Kluster Valkey (mirip dengan Kluster Redis) membagi ruang kunci menjadi 16.384 slot hash, yang didistribusikan secara merata di seluruh node utama dalam kluster.

Di bagian berikut, kami menyiapkan kluster Valkey tiga node dengan tiga replika, memastikan:

  • Cakupan slot penuh (semua 16.384 slot).
  • Ketersediaan tinggi melalui replikasi.
  • Penetapan peran yang tepat dan verifikasi kesehatan kluster.

Menginisialisasi kluster Valkey dengan simpul utama di zona 1 dan 2 dan mengonfigurasi distribusi slot

  • Buat kluster dengan tiga node utama di zona 1 dan 2 dan distribusikan secara merata 16.384 slot hash di seluruhnya menggunakan kubectl exec perintah .

    kubectl exec -it -n valkey valkey-masters-0 -- valkey-cli --cluster create --cluster-yes --cluster-replicas 0 \
                    valkey-masters-0.valkey-masters.valkey.svc.cluster.local:6379 \
                    valkey-masters-1.valkey-masters.valkey.svc.cluster.local:6379 \
                    valkey-masters-2.valkey-masters.valkey.svc.cluster.local:6379 \
                    --pass ${SECRET}

    Contoh output:

    >>> Performing hash slots allocation on 3 nodes...
Master[0] -> Slots 0 - 5460
Master[1] -> Slots 5461 - 10922
Master[2] -> Slots 10923 - 16383
M: ee6ac1d00d3f016b6f46c7ce11199bc1a7809a35 valkey-masters-0.valkey-masters.valkey.svc.cluster.local:6379
   slots:[0-5460] (5461 slots) master
M: fd1fb98db83976478e05edd3d2a02f9a13badd80 valkey-masters-1.valkey-masters.valkey.svc.cluster.local:6379
   slots:[5461-10922] (5462 slots) master
M: ea47bf57ae7080ef03164a4d48b662c7b4c8770e valkey-masters-2.valkey-masters.valkey.svc.cluster.local:6379
   slots:[10923-16383] (5461 slots) master
>>> Nodes configuration updated
>>> Assign a different config epoch to each node
>>> Sending CLUSTER MEET messages to join the cluster
Waiting for the cluster to join
...
>>> Performing Cluster Check (using node valkey-masters-0.valkey-masters.valkey.svc.cluster.local:6379)
M: ee6ac1d00d3f016b6f46c7ce11199bc1a7809a35 valkey-masters-0.valkey-masters.valkey.svc.cluster.local:6379
   slots:[0-5460] (5461 slots) master
M: ea47bf57ae7080ef03164a4d48b662c7b4c8770e 10.224.0.176:6379
   slots:[10923-16383] (5461 slots) master
M: fd1fb98db83976478e05edd3d2a02f9a13badd80 10.224.0.247:6379
   slots:[5461-10922] (5462 slots) master
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.

Tambahkan replika Valkey di zona 3 untuk mengaktifkan ketersediaan tinggi

  • Tambahkan satu replika per simpul utama di zona yang berbeda untuk memastikan toleransi kesalahan dan kemampuan failover otomatis menggunakan perintah berikut kubectl exec .

    kubectl exec -ti -n valkey valkey-masters-0 -- valkey-cli --cluster add-node \
                    valkey-replicas-0.valkey-replicas.valkey.svc.cluster.local:6379 \
                    valkey-masters-0.valkey-masters.valkey.svc.cluster.local:6379  --cluster-slave \
                    --pass ${SECRET}

kubectl exec -ti -n valkey valkey-masters-0 -- valkey-cli --cluster add-node \
                    valkey-replicas-1.valkey-replicas.valkey.svc.cluster.local:6379 \
                    valkey-masters-1.valkey-masters.valkey.svc.cluster.local:6379  --cluster-slave \
                    --pass ${SECRET}

kubectl exec -ti -n valkey valkey-masters-0 -- valkey-cli --cluster add-node \
                    valkey-replicas-2.valkey-replicas.valkey.svc.cluster.local:6379 \
                    valkey-masters-2.valkey-masters.valkey.svc.cluster.local:6379  --cluster-slave \
                    --pass ${SECRET}

    Contoh output:

    >>> Adding node valkey-replicas-0.valkey-replicas.valkey.svc.cluster.local:6379 to cluster valkey-masters-0.valkey-masters.valkey.svc.cluster.local:6379
>>> Performing Cluster Check (using node valkey-masters-0.valkey-masters.valkey.svc.cluster.local:6379)
M: ee6ac1d00d3f016b6f46c7ce11199bc1a7809a35 valkey-masters-0.valkey-masters.valkey.svc.cluster.local:6379
   slots:[0-5460] (5461 slots) master
M: ea47bf57ae7080ef03164a4d48b662c7b4c8770e 10.224.0.176:6379
   slots:[10923-16383] (5461 slots) master
M: fd1fb98db83976478e05edd3d2a02f9a13badd80 10.224.0.247:6379
   slots:[5461-10922] (5462 slots) master
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.
Automatically selected master valkey-masters-0.valkey-masters.valkey.svc.cluster.local:6379
>>> Send CLUSTER MEET to node valkey-replicas-0.valkey-replicas.valkey.svc.cluster.local:6379 to make it join the cluster.
Waiting for the cluster to join
>>> Configure node as replica of valkey-masters-0.valkey-masters.valkey.svc.cluster.local:6379.
[OK] New node added correctly.
>>> Adding node valkey-replicas-1.valkey-replicas.valkey.svc.cluster.local:6379 to cluster valkey-masters-1.valkey-masters.valkey.svc.cluster.local:6379
>>> Performing Cluster Check (using node valkey-masters-1.valkey-masters.valkey.svc.cluster.local:6379)
M: fd1fb98db83976478e05edd3d2a02f9a13badd80 valkey-masters-1.valkey-masters.valkey.svc.cluster.local:6379
   slots:[5461-10922] (5462 slots) master
S: 0ebceb60cbcc31da9040159440a1f4856b992907 10.224.0.224:6379
   slots: (0 slots) slave
   replicates ee6ac1d00d3f016b6f46c7ce11199bc1a7809a35
M: ea47bf57ae7080ef03164a4d48b662c7b4c8770e 10.224.0.176:6379
   slots:[10923-16383] (5461 slots) master
M: ee6ac1d00d3f016b6f46c7ce11199bc1a7809a35 10.224.0.14:6379
   slots:[0-5460] (5461 slots) master
   1 additional replica(s)
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.
Automatically selected master valkey-masters-1.valkey-masters.valkey.svc.cluster.local:6379
>>> Send CLUSTER MEET to node valkey-replicas-1.valkey-replicas.valkey.svc.cluster.local:6379 to make it join the cluster.
Waiting for the cluster to join
>>> Configure node as replica of valkey-masters-1.valkey-masters.valkey.svc.cluster.local:6379.
[OK] New node added correctly.
>>> Adding node valkey-replicas-2.valkey-replicas.valkey.svc.cluster.local:6379 to cluster valkey-masters-2.valkey-masters.valkey.svc.cluster.local:6379
>>> Performing Cluster Check (using node valkey-masters-2.valkey-masters.valkey.svc.cluster.local:6379)
M: ea47bf57ae7080ef03164a4d48b662c7b4c8770e valkey-masters-2.valkey-masters.valkey.svc.cluster.local:6379
   slots:[10923-16383] (5461 slots) master
S: 0ebceb60cbcc31da9040159440a1f4856b992907 10.224.0.224:6379
   slots: (0 slots) slave
   replicates ee6ac1d00d3f016b6f46c7ce11199bc1a7809a35
S: fa44edff683e2e01ee5c87233f9f3bc35c205dce 10.224.0.103:6379
   slots: (0 slots) slave
   replicates fd1fb98db83976478e05edd3d2a02f9a13badd80
M: ee6ac1d00d3f016b6f46c7ce11199bc1a7809a35 10.224.0.14:6379
   slots:[0-5460] (5461 slots) master
   1 additional replica(s)
M: fd1fb98db83976478e05edd3d2a02f9a13badd80 10.224.0.247:6379
   slots:[5461-10922] (5462 slots) master
   1 additional replica(s)
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.
Automatically selected master valkey-masters-2.valkey-masters.valkey.svc.cluster.local:6379
>>> Send CLUSTER MEET to node valkey-replicas-2.valkey-replicas.valkey.svc.cluster.local:6379 to make it join the cluster.
Waiting for the cluster to join
>>> Configure node as replica of valkey-masters-2.valkey-masters.valkey.svc.cluster.local:6379.
[OK] New node added correctly.

Verifikasi peran pod dan status replikasi

  • Konfirmasikan bahwa setiap primer dan replika dikonfigurasi dengan benar dan bahwa hubungan replikasi dibuat menggunakan perintah berikut kubectl exec .

    for x in $(seq 0 2); do echo "valkey-masters-$x"; kubectl exec -n valkey valkey-masters-$x  -- valkey-cli --pass ${SECRET} role; echo; done
for x in $(seq 0 2); do echo "valkey-replicas-$x"; kubectl exec -n valkey valkey-replicas-$x -- valkey-cli --pass ${SECRET} role; echo; done

    Contoh output:

    valkey-masters-0
master
84
10.224.0.224
6379
84
valkey-masters-1
master
84
10.224.0.103
6379
84
valkey-masters-2
master
70
10.224.0.200
6379
70
valkey-replicas-0
slave
10.224.0.14
6379
connected
98
valkey-replicas-1
slave
10.224.0.247
6379
connected
98
valkey-replicas-2
slave
10.224.0.176
6379
connected
84

Langkah berikutnya

Memvalidasi ketahanan kluster Valkey pada AKS

Untuk mempelajari selengkapnya tentang menyebarkan perangkat lunak sumber terbuka di Azure Kubernetes Service (AKS), lihat artikel berikut:

Kontributor

Microsoft mempertahankan artikel ini. Kontributor berikut awalnya menulisnya:

  • Nelly Kiboi | Teknisi Layanan
  • Saverio Proto | Teknisi Pengalaman Pelanggan Utama
  • Don Tinggi | Insinyur Pelanggan Utama
  • LaBrina Mencintai | Teknisi Layanan Utama
  • Ken Kilty | TPM Utama
  • Russell de Pina | TPM Utama
  • Colin Mixon | Manajer Produk
  • Ketan Chawda | Insinyur Pelanggan Senior
  • Naveed Kharadi | Teknisi Pengalaman Pelanggan
  • Erin Schaffer | Pengembang Konten 2
  • Terakhir diperbarui pada