Changelog:
  - use PROPAGATE_UPGRADES env variable to defer update events to core-ui-mw pods
  - set to `false` to only warm up cache
  - re-deploy with set to `true` to actually roll out the upgrade

if redis.auth.enabled was true, the chart did not render successfully.

Implements #21

Helps to observe state in different cache layers

julian.baeume authored 1 year ago and julian.baeume committed 1 year ago

Changelog:
- introduce two separate roles for middleware deployments:
    - ui-middleware: read from redis only, listen to version updates, can easily be scaled
    - updater: split out all code that writes to redis, no need to scale > 1

Just another use case to test. This is supposed to be the desired
mode for core-middleware, so we should at least have this tested as
chances are high that admins want to align on the redis deployment.

This is a breaking change.

Changelog:
- Redis is now mandatory and enabled by default
- Added Sentinel, Standalone and Cluster support
- Standalone mode with sidecar is used by default
  - If no host(s) are configured, a redis sidecar is injected into the deployment
  - No extra configuration needed
  - This is intended for development and does not scale.
- Helm values have changed, see README.md:
  - `redis.host` has been renamed to `redis.hosts` and expects a list of strings with the following pattern: <localhost:6379> (needed for sentinel and cluster modes)
  - `redis.port` has been removed, see `redis.hosts`

fix deployments that did not have this value configured at all
by providing a sensible default.