Include Redis in our helm configuration #95
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Fix #84
This PR includes Redis in our
helm
configuration for future uses.Details and comments
We add the Bitnami's Redis helm configuration to our dependencies.
Now the project can be built (we had problems with the versions but is fixed in this PR) and installed. The user can use all the configurations provided by Bitnami for
redis
but to simplify the initial setup I created a similar configuration that we have in thedocker-compose
.Some changes that we are applying here:
7000
to avoid collisions with the port used byray-dashboard
.standalone
to simplify but the user can configure a replica if it wants.*.tgz
from Redis is ignored by.gitignore
(I was not totally sure about this decision or it we need to upload this file).