[Question]Config multiple Redis server components managed by only one Redis Sentinel component? #8882
-
|
I want to have 2 Redis components managed by only one Redis Sentinel component. Is there any way to achieve this and it is practical to deploy it with this topology in production? Thank you Here is my idea yaml which has 1 Sentinel + 2 Redis Server Components apiVersion: apps.kubeblocks.io/v1alpha1
kind: Cluster
metadata:
name: mycluster
namespace: redis
spec:
terminationPolicy: Delete
clusterDefinitionRef: redis
topology: replication
componentSpecs:
- name: redis
componentDef: redis-7
affinity:
podAntiAffinity: Preferred
topologyKeys:
- kubernetes.io/hostname
tenancy: SharedNode
tolerations:
- key: kb-data
operator: Equal
value: 'true'
effect: NoSchedule
disableExporter: true
enabledLogs:
- running
replicas: 2
resources:
limits:
cpu: '0.5'
memory: 0.5Gi
requests:
cpu: '0.5'
memory: 0.5Gi
volumeClaimTemplates:
- name: data
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 5Gi
storageClassName: local-path
- name: redis-sentinel
componentDef: redis-sentinel-7
disableExporter: false
affinity:
podAntiAffinity: Preferred
topologyKeys:
- kubernetes.io/hostname
tenancy: SharedNode
tolerations:
- key: kb-data
operator: Equal
value: 'true'
effect: NoSchedule
replicas: 3
resources:
limits:
cpu: '0.5'
memory: 0.5Gi
requests:
cpu: '0.5'
memory: 0.5Gi
volumeClaimTemplates:
- name: data
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 20Gi
storageClassName: local-path
- name: redis
componentDef: redis-7
affinity:
podAntiAffinity: Preferred
topologyKeys:
- kubernetes.io/hostname
tenancy: SharedNode
tolerations:
- key: kb-data
operator: Equal
value: 'true'
effect: NoSchedule
disableExporter: true
enabledLogs:
- running
replicas: 2
resources:
limits:
cpu: '0.5'
memory: 0.5Gi
requests:
cpu: '0.5'
memory: 0.5Gi
volumeClaimTemplates:
- name: data
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 5Gi
storageClassName: local-path
# - name: redis-twemproxy
# serviceAccountName: kb-redis-cluster
# replicas: 2
# resources:
# limits:
# cpu: '0.5'
# memory: 0.5Gi
# requests:
# cpu: '0.5'
# memory: 0.5Gi
# services:
# - name: proxy
# serviceType: NodePort |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 4 replies
-
|
@hexknight01 |
Beta Was this translation helpful? Give feedback.
-
|
Hi @Y-Rookie , the Cluster CRD shows this error as I understand the status:
conditions:
- lastTransitionTime: "2025-02-07T03:19:54Z"
message: component redis1 not defined in topology standalone
reason: PreCheckFailed
status: "False"
type: ProvisioningStarted |
Beta Was this translation helpful? Give feedback.
-
|
FYI, I am using version: 0.9.2 |
Beta Was this translation helpful? Give feedback.
-
I apologize, please allow me to correct this. In version 0.9.2, you need to remove the |
Beta Was this translation helpful? Give feedback.
-
|
@Y-Rookie it works as expected. Thank you so much |
Beta Was this translation helpful? Give feedback.
@hexknight01
Hello, the requirement of multiple Redis components sharing a single Redis Sentinel component can be satisfied.
If you want to build such a topology structure in a cluster, there are some issues with the cluster YAML you provided above.
You can no longer define the cluster using the topology method. Instead, you need to customize the cluster YAML directly, as shown below (remove cluster.spec.topology field and customize the Redis component names in cluster.spec.componentSpecs[x].name):