Update decission tree for Redis persistence (#592)

Author: Starefossen

docs/persistence/README.md

@@ -33,6 +33,7 @@ Choose wisely.
 
 ```mermaid
 graph TD
+  F[I need caching!] --> REDIS[Redis]
   A[I got data!] --> B[Is it structured?]
   B --> |Yes| C[Is it events?]
   B --> |No| D[Is it files?]
@@ -43,6 +44,7 @@ graph TD
   E --> |Yes| GBQ[BigQuery]
   E --> |No| GCSQL[Cloud SQL]
 
+  click REDIS "#redis"
   click GBQ "#bigquery"
   click GCS "#cloud-storage-buckets"
   click GCSQL "#cloud-sql"
@@ -55,15 +57,15 @@ graph TD
 Below is a list of the different storage options available to you.
 
 | Name                            | Type        | Recommendation | Availability | Backup |
-|---------------------------------|-------------|:--------------:|:------------:|:------:|
+| ------------------------------- | ----------- | :------------: | :----------: | :----: |
 | [Kafka](#kafka)                 | Streaming   |       ✅        |     All      |  Yes*  |
 | [Cloud Storage](#cloud-storage) | Object      |       ✅        |     GCP      |  Yes*  |
 | [Cloud SQL](#cloud-sql)         | Relational  |       ✅        |     GCP      |  Yes   |
 | [BigQuery](#bigquery)           | Relational  |       ✅        |     GCP      |  Yes*  |
-| [OpenSearch](#opensearch)       | Document    |       ✅        |     All      |  Yes   |
-| [Redis](#redis)                 | Key/Value   |       ✅        |     All      |  Yes   |
-| [InfluxDB](#influxdb)           | Time Series |       ✅        |     All      |  Yes   |
-| [IBM MQ](#ibm-mq)               | Message     |       ⚠️       |     All      |  Yes*  |
+| [OpenSearch](#opensearch)       | Document    |       ✅        |     GCP      |  Yes   |
+| [Redis](#redis)                 | Key/Value   |       ✅        |     GCP      |  Yes   |
+| [InfluxDB](#influxdb)           | Time Series |       ⚠️        |     All      |  Yes   |
+| [IBM MQ](#ibm-mq)               | Message     |       ⚠️        |     All      |  Yes*  |
 
 \* Data is highly available and fault-tolerant but not backed up if deleted by
 mistake.
@@ -111,12 +113,17 @@ OpenSearch offers a drop-in replacement for Elasticsearch.
 ## Redis
 
 Redis is a key value database that is used for storing and querying data. It is
-a good choice for storing data that is not relational in nature.
+a good choice for storing data that is not relational in nature and often used
+for caching.
 
 [:octicons-arrow-right-24: Getting started with Redis](./redis.md)
 
 ## InfluxDB
 
+!!! warning "Outdated"
+
+    Aiven has informed us that they will no longer support InfluxDB in the future. We are currently looking into alternatives.
+
 InfluxDB is a time series database that is used for storing and querying data.
 It is a good choice for storing data that is not relational in nature.
 

docs/persistence/kafka/README.md

@@ -1,3 +1,9 @@
+---
+description: >-
+    Kafka is a distributed streaming platform that can be used to publish and
+    subscribe to streams of records. It is a good alternative to synchronous
+    communication between services if you need to decouple services.
+---
 # Kafka
 
 NAV uses Aiven hosted Kafka.
@@ -17,7 +23,7 @@ To get started, see [accessing topics from an application](manage_topics.md#acce
     Kafka as a system is highly durable, and is designed to be able to keep your data safe in the event of a failure.
     This requires a properly configured replication factor for your topic, and that your clients use the appropriate strategy when sending messages and committing offsets.
     Even so, our recommendation is that Kafka should not be the master of your data, and you should have the ability to restore your data from some other system.
-    
+
 
 ## Status and roadmap
 

docs/persistence/redis.md

@@ -42,7 +42,7 @@ The environment variables use a fixed prefix, and the instance name uppercased a
 Example for the sessions instance used above:
 
 | Key                     | Value                                                                                                                                        |
-|-------------------------|----------------------------------------------------------------------------------------------------------------------------------------------|
+| ----------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- |
 | REDIS_URI_SESSIONS      | The URI for the Redis instance, typically with a `rediss` scheme. <br/>Example:  `rediss://redis-team-sessions-nav-dev.aivencloud.com:26483` |
 | REDIS_USERNAME_SESSIONS | The username to use when connecting.                                                                                                         |
 | REDIS_PASSWORD_SESSIONS | The password to use when connecting.                                                                                                         |
@@ -58,7 +58,7 @@ We recommend creating your Redis instances in their own workflow for more contro
 Creating a Redis instance is done by adding a Redis resource to your namespace with detailed configuration.
 Some configuration is enforced by the nais platform, while the rest is up to the users.
 
-Earlier we talked about the "instance name". 
+Earlier we talked about the "instance name".
 In reality, the actual name of the redis instance will be `redis-<team name>-<instance name>` (where `team name` is the same as the namespace your application resides in).
 The resource needs to have this full name in order to be accepted.
 
@@ -81,8 +81,8 @@ spec:
 A minimal Redis resource only requires `plan` and `project`.
 
  * `project` should match your nais tenant (`nav`, `mtpilot`, `ssb` or `fhi`) and the environment you are running in (ex. `dev`, `prod`), with a dash (`-`) in between.
- * `plan` is the Aiven plan for your Redis instance. 
-   See Aivens list of [possible plan values](https://aiven.io/pricing?product=redis). 
+ * `plan` is the Aiven plan for your Redis instance.
+   See Aivens list of [possible plan values](https://aiven.io/pricing?product=redis).
    The values are lowercased.
    Make sure you understand the differences between the plans before selecting the one you need.
    Examples: `startup-4`, `startup-56`, `business-4`, `premium-14`.
@@ -102,23 +102,22 @@ Business plans are backed up every 12 hours, keeping 3 days of backups available
 
 Once the resource is added to the cluster, some additional fields are filled in by the platform and should be left alone unless you have a good reason:
 
-| field                   |                                                                                                       | 
-|-------------------------|-------------------------------------------------------------------------------------------------------|
+| field                   |                                                                                                       |
+| ----------------------- | ----------------------------------------------------------------------------------------------------- |
 | `projectVpcId`          | Ensures the instance is connected to the correct project VPC and is not available on public internet. |
 | `tags`                  | Adds tags to the instance used for tracking billing in Aiven.                                         |
-| `cloudName`             | Where the Redis instance should run.                                                                  |  
+| `cloudName`             | Where the Redis instance should run.                                                                  |
 | `terminationProtection` | Protects the instance against unintended termination. Must be set to `false` before deletion.         |
 
 There are some fields available that should not be used:
 
 | field                  |                                                                                                 |
-|------------------------|-------------------------------------------------------------------------------------------------|
+| ---------------------- | ----------------------------------------------------------------------------------------------- |
 | `authSecretRef`        | Reference to a secret containing an Aiven API token. Provided via other mechanisms.             |
 | `connInfoSecretTarget` | Name of secret to put connection info in, not used as nais provides these via other mechanisms. |
 | `projectVPCRef`        | Not used since we use `projectVpcId`.                                                           |
 | `serviceIntegrations`  | Not used at this time.                                                                          |
 
-
 # Legacy Redis documentation
 
 This is the documentation for how you could run Redis on NAIS yourself, kept here for reference for those teams that continue to run Redis this way.
@@ -272,7 +271,7 @@ An example Redis setup looks like this:
           rules:
             - application: ${appname}-redisexporter
       envFrom:
-        - secret: ${secret-name} 
+        - secret: ${secret-name}
     ---
     apiVersion: "nais.io/v1alpha1"
     kind: "Application"