Skip to content
Snippets Groups Projects
Verified Commit 283004a5 authored by Maarten de Waard's avatar Maarten de Waard :angel:
Browse files

update default values and some other files for new Redis chart version

parent c342b451
No related branches found
No related tags found
1 merge request!48Update Helm release redis to v15
## Unreleased
* Update redis chart to version 15
* BREAKING: This needs a re-install of the Redis release (this should be OK
because redis is only for caching). This also needs you to move the
following variables:
- `redis.password` is now `redis.auth.password`
- `redis.cluster.enabled` is now `redis.architecture`, which takes values
"standalone" and "replication" (this chart defaults to standalone).
- See [the Redis chart upgrade
guide](https://github.com/bitnami/charts/tree/master/bitnami/redis#upgrading)
for other changes
## [0.3.1] - 2021-09-30
* Fix database service name for standalone architecture
......
......@@ -9,8 +9,9 @@ helm delete $releaseName
## Delete remaining PVCs:
kubectl delete pvc \
data-$releaseName-database-master-0 \
data-$releaseName-database-slave-0 \
data-$releaseName-mariadb-0
data-$releaseName-database-primary-0 \
data-$releaseName-database-secondary-0 \
redis-data-$releaseName-redis-master-0 \
redis-data-$releaseName-redis-slave-0 \
redis-data-$releaseName-redis-slave-1
......
......@@ -133,16 +133,16 @@ redis:
# configured to connect to this Redis and `Redis Object Cache` plugin will be
# installed as a conventional plugin.
enabled: false
# password: <SET A REDIS PASSWORD HERE>
# master:
# persistence:
# # Set persistence to true you want redis to have persistence
# enabled: false
# # disableCommand is set as null to enable FLUSHALL and FLUSHDB and allow cache purge and flush
# disableCommands: []
# cluster:
# #Set redis.cluster.enabled as true to have a master and a slave redis. Not necessary for caching
# enabled: false
# auth:
  • This change to the config structure was not carried over to values.yaml, resulting in a failed Redis connection from PhpRedis to the database itself on fresh deployments. I've submitted an issue with the one-liner fix detailed within: #113 (closed)

  • Please register or sign in to reply
# password: <SET A REDIS PASSWORD HERE>
# master:
# persistence:
# # Set persistence to true you want redis to have persistence
# enabled: false
# # disableCommand is set as null to enable FLUSHALL and FLUSHDB and allow cache purge and flush
# disableCommands: []
# # Set architecture to "replication" to have a primary and secondary redis. Not necessary for caching
# architecture: "replication"
......
......@@ -310,9 +310,7 @@ redis:
enabled: false
# disableCommand is set as null to enable FLUSHALL and FLUSHDB and allow cache purge and flush
disableCommands: []
cluster:
# Set redis.cluster.enabled as true to have a master and a slave redis. Not necessary for caching
enabled: false
architecture: "standalone"
backup:
enabled: false
......
# Set the docker image tag to the name of the current branch.
# Shortened to 63 bytes because Gitlab does the same with the `CI_COMMIT_REF_SLUG`
# variable, which we use in the CI script to build the docker image.
dockerTag=$(git rev-parse --abbrev-ref HEAD | cut -b "-63")
# Backslashes are replaced with '-'.
dockerTag=$(git rev-parse --abbrev-ref HEAD | cut -b "-63" | sed -e 's/[\/\.]/-/g')
# Only get the number from the issue (or whatever is in front of a dash
# otherwise) for the release name
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment