A golang based redis operator that will make/oversee Redis standalone/cluster/replication/sentinel mode setup on top of the Kubernetes.
731
stars
206
forks
source link
Redis Sentinel pods not starting after redis-operator upgrade #995
Closed
MoZadro closed 1 week ago
What version of redis operator are you using?
Version 0.15.9 quay.io/opstree/redis-operator:v0.15.1
We are using same image on both redis-operator versions image: quay.io/opstree/redis-sentinel:v7.0.12
On this redis-operator version everything is ok.
Statefulset of Redis Sentinel, probes (both liveness and readiness) are checking:
Does this issue reproduce with the latest release?
When we upgrade redis-operator version to 0.16.1 ghcr.io/ot-container-kit/redis-operator/redis-operator:v0.17.0
Then Redis Sentinel pods wont start, looks like probes (both liveness and readiness) are not checking healthcheck.sh script anymore but:
but under containers env variables,
SENTINEL_PORT env is not defined.
What did you do?
When we configure/add manually to Sentinel StatefulSet
Then pods are in Running state
What did you expect to see?
We expect that pods are in running state, like on older redis-operator version.