EPIC Goal

Automate and validate Redis cache setup for RHDH

Background/Feature Origin

To improve performance and reliability of RHDH, we need to implement cache stores for the Backstage backend.

Why is this important?

Implementing Redis as a cache store will enable scale-out of RHDH instances, improving overall system performance and reliability.

User Scenarios

• As a DevOps engineer, I want to easily set up Redis cache for RHDH in a namespace.
• As a system administrator, I want to connect RHDH to an external cache seamlessly.
• As a QA engineer, I want to validate the usage of cache with the RBAC plugin in a scaled-out deployment.

Dependencies (internal and external)

• Red Hat supported Redis 7 image
• RBAC plugin team for cache integration

Acceptance Criteria

• Automated setup of Redis in a RHDH namespace is implemented and functional
• Automated connection of RHDH to an external cache is implemented and verified
• Automated validation of cache usage with RBAC plugin is implemented, including:
  • Scaling out deployment to 2 pods
  • Checking specific keys in Redis
• Developer setup for testing local Redis setups with containers is provided
• Cache functionality in horizontally scaled RHDH deployments is validated

Release Enablement/Demo - Provide necessary release enablement details and documents
DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
DEV - Downstream build attached to advisory: <link to errata>
QE - Test plans in Playwright: <link or reference to playwright>
QE - Automated tests merged: <link or reference to automated tests>
DOC - Downstream documentation merged: <link to meaningful PR>