-
Notifications
You must be signed in to change notification settings - Fork 524
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: reintroduce "Extend Redis functionality" #1492
Conversation
- Adds support to set REDIS_PASSWORD as a kubernetes secret. - Adds support to set externalredis.db too choose the db number - Adds support to use externalredis.ssl for secure ssl - Adds support to set externalredis.brokerUrl, this overrides the BROKER_URL environment variable that is used to set the broker with a secret.
06fbf27
to
32b4476
Compare
@Mokto Please let me know if there is anything else I need to update. Thanks! Update: Seems like the linting pipeline is failing because of |
I see in log
|
…cret are empty (another location)
Thanks for the response! I have fixed that problem but now I'm seeing
in the pipeline now |
…ubchart credential and referenced credential in Sentry deployments
Not really sure what is going on with these failed E2E tests.. I tried doing a dry-run between a passing build and my local one:
I don't see any actual difference that can cause issues |
…asswords are defined
@Mokto, it seems like my changes have passed the pipeline. May you take a look? Thank you :) |
… broke S3 existing secret (from commit 0b7a7b4)
This PR reintroduces #914 with conflicts resolved.
Core Diff:
redis.auth.password
etc., this is because subchart relies on that path to create authentication so settingredis.password
only will only break the integrated Redis connection (because Redis subchart will believe there is no password defined).