You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We created the Redis cluster with exporter functionality enabled.
Then we disabled the exporter functionality by setting spec.redisExporter.enabled to false.
But we found that the service objects for both RedisLeader and RedisFollowers still have the exporter port open.
What version of redis operator are you using?
redis-operator version: We are using redis-operator built from the
HEAD
Does this issue reproduce with the latest release?
no tested
What operating system and processor architecture are you using (
kubectl version
)?kubectl version
OutputWhat did you do?
We created the Redis cluster with exporter functionality enabled.
Then we disabled the exporter functionality by setting
spec.redisExporter.enabled
tofalse
.But we found that the service objects for both RedisLeader and RedisFollowers still have the exporter port open.
What did you expect to see?
All exporter related functionalities are removed, and the exporter port no longer exposed
What did you see instead?
The service objects still have exporter port open
The text was updated successfully, but these errors were encountered: