fix: exporter no auth to redis

[drivebyer]

Description

Fixes #724

Type of change

• Bug fix (non-breaking change which fixes an issue)

Checklist

• Tests have been added/modified and all tests pass.
• Functionality/bugs have been confirmed to be unchanged or fixed.
• I have performed a self-review of my own code.
• Documentation has been updated or added where necessary.

Additional Context

[gitguardian]

⚠️ GitGuardian has uncovered 3 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	Secret	Commit	Filename
-	Generic Password	0a9f710	tests/e2e-chainsaw/v1beta2/password/redis-cluster/secret.yaml	View secret
-	Generic Password	0a9f710	tests/e2e-chainsaw/v1beta2/password/redis-standalone/secret.yaml	View secret
-	Generic Password	0a9f710	tests/e2e-chainsaw/v1beta2/password/redis-replication/secret.yaml	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

<sup>🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Our GitHub checks need improvements? Share your feedbacks!</sup>

[codecov]

Codecov Report

Attention: 13 lines in your changes are missing coverage. Please review.

Comparison is base (c8fd3bd) 28.75% compared to head (a6a4e2c) 28.74%.

❗ Current head a6a4e2c differs from pull request most recent head ed85bdf. Consider uploading reports for the commit ed85bdf to get more accurate results

Files	Patch %	Lines
k8sutils/statefulset.go	18.75%	12 Missing and 1 partial ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #743      +/-   ##
==========================================
- Coverage   28.75%   28.74%   -0.01%     
==========================================
  Files          19       19              
  Lines        3269     3287      +18     
==========================================
+ Hits          940      945       +5     
- Misses       2295     2307      +12     
- Partials       34       35       +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[drivebyer]

⚠️ GitGuardian has uncovered 3 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request
🛠 Guidelines to remediate hardcoded secrets
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.Our GitHub checks need improvements? Share your feedbacks!

This pr change e2e password from Opstree@1234 to Opstree1234. Because the exporter mistinguish it with @ in address.

[shubham-cmyk]

LGTM