Open slax81 opened 1 year ago
@slax81 have you been able to workaround this issue?
@njohnstone2 No, had to use redis from the chart
@njohnstone2 @slax81 this worked for me (in values file) to get external redis working with elasticache (no sentinel):
env:
- name: REDIS_USERNAME
value: ""
- name: REDIS_PASSWORD
value: ""
- name: REDIS_HOST
value: "whatever.use1.cache.amazonaws.com"
- name: REDIS_PORT
value: "6379"
- name: REDIS_PROTOCOL
value: "redis"
Hi, I would like to take a closer look at this issue regarding the Sentinel configuration, specifically adding options for hosts where the ports may vary. Before I start implementing any changes, I wanted to reach out to see if the authors have any specific thoughts or preferences on how they envision the implementation. Your insights would be greatly appreciated and will help ensure that the changes align with the project's direction. Thank you!
I also would like to setup an ExternalRedis (Standalone though) that does not need a password.
What went wrong?
What happened:
OnCall helm chart can't work with an external Redis instance that has no authentication, also there are no options to set up sentinel configuration.
Also, passwordkey field for the external rabbitmq password is incorrect. Should be: the key in the secret containing the rabbitmq password passwordKey: rabbitmq-password
What did you expect to happen:
How do we reproduce it?
Grafana OnCall Version
v1.2.44
Product Area
Helm
Grafana OnCall Platform?
Kubernetes
User's Browser?
No response
Anything else to add?
No response