docs: Remove Redis from docs (#6289)

Author: keydunov

docs/content/Caching/Overview.mdx

@@ -16,10 +16,7 @@ menuOrder: 1
 </div>
 
 Cube provides a two-level caching system. The first level is **in-memory** cache
-and is active by default. Currently, [Redis][link-redis] is being used for
-in-memory cache and queue management for [clustered Cube
-deployments][ref-production-checklist]. Cube Store will [replace
-Redis][replace-redis] in late 2022.
+and is active by default.
 
 Cube's [in-memory cache](#in-memory-cache) acts as a buffer for your database
 when there's a burst of requests hitting the same data from multiple concurrent

docs/content/Caching/Running-in-Production.mdx

@@ -7,18 +7,9 @@ menuOrder: 4
 
 Cube makes use of two different kinds of cache:
 
-- Redis, for in-memory storage of query results
-- Cube Store for storing pre-aggregations
+- In-memory storage of query results
+- Pre-aggregations
 
-In development, Cube uses in-memory storage on the server. In production, we
-**strongly** recommend running Redis as a separate service.
-
-<WarningBox>
-
-Cube Store [will replace Redis][replace-redis] for in-memory cache and queue
-management in late 2022.
-
-</WarningBox>
 
 Cube Store is enabled by default when running Cube in development mode. In
 production, Cube Store **must** run as a separate process. The easiest way to do

docs/content/Deployment/Overview.mdx

@@ -15,15 +15,11 @@ production. You can find platform-specific guides for:
 - [Cube Cloud][ref-deploy-cubecloud]
 - [Docker][ref-deploy-docker]
 
-For information on how to deploy Cube using Kubernetes, please check out the examples for
-[Kubernetes][gh-cube-examples-k8s]. You can also check out [Helm Charts](https://artifacthub.io/packages/search?repo=gadsme) from our community members. Please note these examples are community-contributed, and not
-officially supported by Cube.
-
 If you are moving Cube to production, check out the [Production
 Checklist][ref-deploy-prod-list].
 
 As shown in the diagram below, a typical production Cube cluster consists of one
-or multiple API instances, a Refresh Worker, Redis and a Cube Store cluster.
+or multiple API instances, a Refresh Worker and a Cube Store cluster.
 
 <div style="text-align: center">
   <img
@@ -40,10 +36,6 @@ Worker** builds and refreshes pre-aggregations in the background. **Cube Store**
 ingests pre-aggregations built by Refresh Worker and responds to queries from
 API instances.
 
-**Redis** is used to manage the queue and query-level cache. Please note, we are
-planning to [replace Redis with Cube Store][replace-redis] for in-memory cache
-and queue management in late 2022.
-
 API instances and Refresh Worker can be configured via [environment
 variables][ref-config-env] or [cube.js configuration file][ref-config-js]. They
 also need access to the data schema files.
@@ -68,16 +60,13 @@ services:
 
       - CUBEJS_CUBESTORE_HOST=cubestore_router
 
-      - CUBEJS_REDIS_URL=redis://redis:6379
-
       - CUBEJS_API_SECRET=secret
     volumes:
       - .:/cube/conf
     depends_on:
       - cubestore_worker_1
       - cubestore_worker_2
       - cube_refresh_worker
-      - redis
 
   cube_refresh_worker:
     image: cubejs/cube
@@ -89,8 +78,6 @@ services:
 
       - CUBEJS_CUBESTORE_HOST=cubestore_router
 
-      - CUBEJS_REDIS_URL=redis://redis:6379
-
       - CUBEJS_API_SECRET=secret
 
       - CUBEJS_REFRESH_WORKER=true
@@ -132,13 +119,6 @@ services:
       - .cubestore:/cube/data
     depends_on:
       - cubestore_router
-
-  redis:
-    image: bitnami/redis:latest
-    environment:
-      - ALLOW_EMPTY_PASSWORD=yes
-    logging:
-      driver: none
 ```
 
 ## API Instance
@@ -292,63 +272,6 @@ services:
       - cubestore_router
 ```
 
-## Redis
-
-<WarningBox>
-
-Cube Store [will replace Redis][replace-redis] for in-memory cache and queue
-management in late 2022.
-
-</WarningBox>
-
-Cube uses Redis, an in-memory data structure store, for query caching and queue.
-
-Set the `CUBEJS_REDIS_URL` environment variable to allow Cube API Instances and
-Refresh Worker to connect to Redis. If your Redis instance also has a password,
-please set it via the `CUBEJS_REDIS_PASSWORD` environment variable. Set the
-`CUBEJS_REDIS_TLS` environment variable to true if you want to enable
-SSL-secured connections. Ensure your Redis cluster allows at least 15 concurrent
-connections.
-
-### <--{"id" : "Redis"}--> Redis Sentinel
-
-Cube supports Redis Sentinel via `CUBEJS_REDIS_USE_IOREDIS=true` environment
-variable. Then set `CUBEJS_REDIS_URL` to the
-`redis+sentinel://localhost:26379,otherhost:26479/mymaster/5` to allow Cube to
-connect to the Redis Sentinel.
-
-Cube server instances used by same tenant environments should have same Redis
-instances. Otherwise they will have different query queues which can lead to
-incorrect pre-aggregation states and intermittent data access errors.
-
-### <--{"id" : "Redis"}--> Redis Pool
-
-If `CUBEJS_REDIS_URL` is provided Cube, will create a Redis connection pool with
-a minimum of 2 and maximum of 1000 concurrent connections, by default. The
-`CUBEJS_REDIS_POOL_MIN` and `CUBEJS_REDIS_POOL_MAX` environment variables can be
-used to tweak pool size limits. To disable connection pooling, and instead
-create connections on-demand, you can set `CUBEJS_REDIS_POOL_MAX` to 0.
-
-If your maximum concurrent connections limit is too low, you may see
-`TimeoutError: ResourceRequest timed out` errors. As a rule of a thumb, you need
-to have `Queue Size * Number of tenants` concurrent connections to ensure the
-best performance possible. If you use clustered deployments, please make sure
-you have enough connections for all Cube server instances. A lower number of
-connections still can work, however Redis becomes a performance bottleneck in
-this case.
-
-### <--{"id" : "Redis"}--> Running without Redis
-
-If you want to run Cube in production without Redis, you can use
-`CUBEJS_CACHE_AND_QUEUE_DRIVER` environment variable to `memory`.
-
-<WarningBox>
-
-Clustered deployments can't be run without Redis as it is used to manage the
-query queue.
-
-</WarningBox>
-
 [dh-cubejs]: https://hub.docker.com/r/cubejs/cube
 [dh-cubestore]: https://hub.docker.com/r/cubejs/cubestore
 [gh-cube-examples-k8s]:

docs/content/Deployment/Production-Checklist.mdx

@@ -49,7 +49,7 @@ CUBEJS_REFRESH_WORKER=true
 
 ## Set up Cube Store
 
-Cube Store is the purpose-built pre-aggregations storage for Cube. Follow the
+Cube Store manages in-memory cache, queue and pre-aggregations for Cube. Follow the
 [instructions here][ref-caching-cubestore] to set it up.
 
 Depending on your database, Cube may need to "stage" pre-aggregations inside
@@ -69,78 +69,6 @@ configured database][ref-config-connect-db] to set it up.
 
 </InfoBox>
 
-## Set up Redis
-
-<WarningBox>
-
-Cube Store [will replace Redis][replace-redis] for in-memory cache and queue
-management in late 2022.
-
-</WarningBox>
-
-Cube requires [Redis](https://redis.io/), an in-memory data structure store, to
-run in production.
-
-It uses Redis for query caching and queue. Set the
-[`CUBEJS_REDIS_URL`][ref-conf-ref-env-redis-url] environment variable to allow
-Cube to connect to Redis. If your Redis instance also has a password, please set
-it via the [`CUBEJS_REDIS_PASSWORD`][ref-conf-ref-env-redis-pass] environment
-variable. Set the [`CUBEJS_REDIS_TLS`][ref-conf-ref-env-redis-tls] environment
-variable to `true` if you want to enable SSL-secured connections. Ensure your
-Redis cluster allows at least 15 concurrent connections.
-
-### <--{"id" : "Set up Redis"}--> Redis Sentinel
-
-Redis provides functionality for high availability through [Redis
-Sentinel][link-redis-sentinel].
-
-For Redis Sentinel support, the npm package [`ioredis`][gh-ioredis] needs to be
-used instead of[`redis`][gh-node-redis]. This is done by setting the
-[`CUBEJS_REDIS_USE_IOREDIS`][ref-conf-ref-env-redis-ioredis] environment
-variable to `true`. Then set [`CUBEJS_REDIS_URL`][ref-conf-ref-env-redis-url] to
-the `redis+sentinel://localhost:26379,otherhost:26479/mymaster/5` to allow Cube
-to connect to the Redis Sentinel.
-
-<WarningBox>
-
-Cube server instances used by same tenant environments should have same Redis
-instances. Otherwise they will have different query queues which can lead to
-incorrect pre-aggregation states and intermittent data access errors.
-
-</WarningBox>
-
-### <--{"id" : "Set up Redis"}--> Redis Pool
-
-If [`CUBEJS_REDIS_URL`][ref-conf-ref-env-redis-url] is provided, Cube will
-create a Redis connection pool with a minimum of `2` and maximum of `1000`
-concurrent connections, by default. The
-[`CUBEJS_REDIS_POOL_MIN`][ref-conf-ref-env-redis-poolmin] and
-[`CUBEJS_REDIS_POOL_MAX`][ref-conf-ref-env-redis-poolmax] environment variables
-can be used to tweak pool size limits. To disable connection pooling, and
-instead create connections on-demand, you can set
-[`CUBEJS_REDIS_POOL_MAX`][`cubejs_redis_pool_max`] to `0`.
-
-If your maximum concurrent connections limit is too low, you may see
-`TimeoutError: ResourceRequest timed out` errors. As a rule of a thumb, you need
-to have `Queue Size * Number of tenants` concurrent connections to ensure the
-best performance possible. If you use clustered deployments, please make sure
-you have enough connections for all Cube server instances. A lower number of
-connections still can work, however Redis becomes a performance bottleneck in
-this case.
-
-### <--{"id" : "Set up Redis"}--> Running without Redis
-
-If you want to run Cube in production without Redis, you can use
-[`CUBEJS_CACHE_AND_QUEUE_DRIVER`][ref-conf-ref-env-cachequeue-driver]
-environment variable to `memory`.
-
-<WarningBox>
-
-Serverless and clustered deployments can't be run without Redis as it is used to
-manage the query queue.
-
-</WarningBox>
-
 ## Secure the deployment
 
 If you're using JWTs, you can configure Cube to correctly decode them and inject