since quite some time we do not report the pod as unhealthy any longer
if redis connection is gone. So in case the connection is lost, we want it
to reconnect.

Make sure to always fetch from redis once client (re-)connected.

name can be too long for some feature branches, makes sure it's as short as possible

Bumps [fastify-metrics](https://github.com/SkeLLLa/fastify-metrics) from 10.3.0 to 10.3.1.
- [Release notes](https://github.com/SkeLLLa/fastify-metrics/releases)
- [Changelog](https://github.com/SkeLLLa/fastify-metrics/blob/master/docs/CHANGELOG.md)
- [Commits](https://github.com/SkeLLLa/fastify-metrics/compare/v10.3.0...v10.3.1)

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

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

Bumps [bull](https://github.com/OptimalBits/bull) from 4.10.4 to 4.11.3.
- [Release notes](https://github.com/OptimalBits/bull/releases)
- [Changelog](https://github.com/OptimalBits/bull/blob/develop/CHANGELOG.md)
- [Commits](https://github.com/OptimalBits/bull/compare/v4.10.4...v4.11.3)

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.

UI Middleware instance for prefix deployments was not restarted, so deployment could be "old".
Online help was broken for prefix deployments, adjusted virtualservice to match deployment