Sentinel.conf missing auth-pass

[Leo791]

Is your feature request related to a problem? Please describe.

When starting sentinels with authentication enabled we get the following logs back:

I529914@R9QGLCQWLP ~ % kubectl logs pod/redis-test007-sentinel-0 -n redis-test007 -f
ACL_MODE is not true, skipping ACL file modification
Starting  sentinel service .....
1:X 16 Jan 2025 17:30:40.404 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:X 16 Jan 2025 17:30:40.404 # Redis version=6.2.14, bits=64, commit=00000000, modified=0, pid=1, just started
1:X 16 Jan 2025 17:30:40.404 # Configuration loaded
1:X 16 Jan 2025 17:30:40.496 * monotonic clock: POSIX clock_gettime
1:X 16 Jan 2025 17:30:40.510 * Running mode=sentinel, port=26379.
1:X 16 Jan 2025 17:30:40.524 # Sentinel ID is fc05fdfc7d4f86d6bc78c53b0de97481fdb46695
1:X 16 Jan 2025 17:30:40.524 # +monitor master mymaster 10.244.3.252 6379 quorum 2
1:X 16 Jan 2025 17:31:10.471 # +sdown master mymaster 10.244.3.252 6379
1:signal-handler (1737049053) Received SIGTERM scheduling shutdown...
1:X 16 Jan 2025 17:37:33.926 # User requested shutdown...
1:X 16 Jan 2025 17:37:33.926 * Removing the pid file.
1:X 16 Jan 2025 17:37:33.931 # Sentinel is now ready to exit, bye bye...

Which shows us that the sentinels cannot connect to the replicas or with each other.

Describe alternatives you've considered

If we add sentinel auth-pass mymaster "password" to sentinel.conf this issue is fixed.

Describe the solution you'd like

Ideally this would be added to the sentinel conf at bootstrap via the sentinel-entrypoint.sh.

What version of redis-operator are you using?

redis-operator version: v0.18.0