Add Redis as a cache and database

[Miranlfk]

Purpose

This pull request introduces Redis as an optional backend for both caching and runtime database in the Thunder deployment pipelines. It adds flexible configuration to deploy and use Redis, including automated installation, network policy, and performance-tuned settings. The changes allow choosing between Postgres and Redis for the runtime DB, and between disabled, in-memory, or Redis for the cache, with all necessary pipeline and Helm chart integration.

Key changes:

Pipeline parameterization and integration:

• Added RUNTIME_DB_TYPE and CACHE_MODE parameters to deploy-thunder.yaml, perf-test-execution.yaml, and Thunder install/reinstall templates, allowing selection of Postgres or Redis for the runtime DB and flexible cache backend. [1] [2] [3] [4]
• Updated variables and job dependencies to propagate and use these parameters throughout the pipeline, ensuring the correct backend is installed and configured. [1] [2] [3] [4] [5] [6] [7] [8] [9]

Redis installation and configuration:

• Introduced a new install_redis job and supporting template (install-redis.yaml) that installs Redis using a Bitnami Helm chart, applies a network policy to allow Thunder access, and optionally deploys RedisInsight for monitoring. [1] [2] [3]
• Added a performance-tuned redis-values.yaml for Redis Helm deployments, and a redis-network-policy.yaml to securely enable cross-namespace access from Thunder to Redis. [1] [2]

Thunder deployment enhancements:

• Modified Thunder install/reinstall scripts to dynamically configure Helm chart values based on the selected cache and runtime DB backends, including Redis connection details and key prefixes when applicable. [1] [2] [3]

Resource configuration:

• Added new variables for Redis resource requests/limits, autoscaling, and addressing, ensuring Redis is provisioned with appropriate resources for high-concurrency scenarios.

Licensing and documentation:

• Added copyright and license headers to new files. [1] [2] [3]

These changes make the Thunder deployment pipelines more flexible and scalable by supporting Redis as a high-performance backend for both caching and runtime database needs.