K8s: 8.2.0 Duckburg release docs

content/embeds/k8s/admission_webhook.md

@@ -30,6 +30,10 @@ webhooks:
           - redisenterprisedatabases
           - redisenterpriseactiveactivedatabases
           - redisenterpriseremoteclusters
+          - redisenterpriseacls
+          - redisenterpriseclusterroles
+          - redisenterpriseusers
+          - redisenterpriseroles
     sideEffects: None
     timeoutSeconds: 30
 ```

content/embeds/k8s/log_collector_role_all_mode.md

@@ -160,6 +160,12 @@ rules:
   - redisenterprisedatabases.app.redislabs.com
   - redisenterpriseremoteclusters.app.redislabs.com
   - redisenterpriseactiveactivedatabases.app.redislabs.com
+  - redisenterpriseacls.app.redislabs.com
+  - redisenterpriseusers.app.redislabs.com
+  - redisenterpriseclusterroles.app.redislabs.com
+  - redisenterpriseclusterrolebindings.app.redislabs.com
+  - redisenterpriseroles.app.redislabs.com
+  - redisenterpriserolebindings.app.redislabs.com
   verbs:
   - get
   - list

content/embeds/k8s/log_collector_role_restricted_mode.md

@@ -141,6 +141,12 @@ rules:
   - redisenterprisedatabases.app.redislabs.com
   - redisenterpriseremoteclusters.app.redislabs.com
   - redisenterpriseactiveactivedatabases.app.redislabs.com
+  - redisenterpriseacls.app.redislabs.com
+  - redisenterpriseusers.app.redislabs.com
+  - redisenterpriseclusterroles.app.redislabs.com
+  - redisenterpriseclusterrolebindings.app.redislabs.com
+  - redisenterpriseroles.app.redislabs.com
+  - redisenterpriserolebindings.app.redislabs.com
   verbs:
   - list
   - get

content/embeds/k8s/openshift_rec.md

@@ -1,39 +1,3 @@
 ```yaml
-apiVersion: app.redislabs.com/v1
-kind: RedisEnterpriseCluster
-metadata:
-  name: rec
-  labels:
-    app: redis-enterprise
-spec:
-  # The number of Redis Enterprise nodes in the clusters.
-  nodes: 3
 
-  persistentSpec:
-    # Whether to enable persistent storage for the Redis Enterprise nodes.
-    enabled: true
-
-    # The size of the persistent volume for each Redis Enterprise node.
-    volumeSize: 20Gi
-
-  # The resources allocated to each Redis Enterprise node.
-  redisEnterpriseNodeResources:
-    requests:
-      cpu: 2
-      memory: 4Gi
-    limits:
-      cpu: 2
-      memory: 4Gi
-
-  redisEnterpriseImageSpec:
-    repository: registry.connect.redhat.com/redislabs/redis-enterprise
-    versionTag: 8.0.18-23
-  redisEnterpriseServicesRiggerImageSpec:
-    repository: registry.connect.redhat.com/redislabs/services-manager
-  bootstrapperImageSpec:
-    repository: registry.connect.redhat.com/redislabs/redis-enterprise-operator
-  usageMeter:
-    callHomeClient:
-      imageSpec:
-        repository: registry.connect.redhat.com/redislabs/call-home-client
 ```

content/embeds/k8s/openshift_role.md

@@ -180,7 +180,6 @@ rules:
       - route.openshift.io
     resources:
       - routes
-      - routes/custom-host
     verbs:
       - create
       - delete
@@ -189,6 +188,13 @@ rules:
       - patch
       - update
       - watch
+  - apiGroups:
+      - route.openshift.io
+    resources:
+      - routes/custom-host
+    verbs:
+      - create
+      - update
   - apiGroups:
       - security.openshift.io
     resourceNames:

content/embeds/k8s/rerc.md

@@ -17,7 +17,7 @@ spec:
 
   # The database URL suffix, will be used for the active-active
   # database replication endpoint and replication endpoint SNI.
-  dbFqdnSuffix: .example-new-york-1-ns1.redislabs.com
+  dbFqdnSuffix: -example-new-york-1-ns1.redislabs.com
 
   # The name of the secret containing cluster credentials.
   # Needs to be formatted as: "redis-enterprise-<RERC name>"

content/operate/_index.md

@@ -45,9 +45,9 @@ hideListLinks: true
 | | <nobr>{{<color-bubble color="bg-blue-bubble" >}} Redis</nobr> Cloud | <nobr>{{<color-bubble color="bg-yellow-bubble">}} Redis</nobr> Software | <nobr>{{<color-bubble color="bg-purple-bubble">}} Redis</nobr> Open Source | <nobr><div class="h-3 w-3 rounded-md border border-redis-pen-600 inline-block mr-1" style="background-color: #8A99A0"></div> Redis for</nobr> Kubernetes |
 |:-----------|:--------------|:-----------|:--------------|:--------------|
 | Transport Layer Security (TLS) | [TLS]({{<relref "/operate/rc/security/database-security/tls-ssl">}}) | [TLS]({{<relref "/operate/rs/security/encryption/tls">}}) | [TLS]({{< relref "/operate/oss_and_stack/management/security/encryption" >}}) | [REDB tlsMode]({{<relref "/operate/kubernetes/reference/api/redis_enterprise_database_api/#spec">}}) |
-| Role-based access control (RBAC) | [Role-based access control]({{<relref "/operate/rc/security/access-control/data-access-control/role-based-access-control">}}) | [Access control]({{<relref "/operate/rs/security/access-control">}}) | [Access control list]({{< relref "/operate/oss_and_stack/management/security/acl" >}}) | [REC credentials]({{<relref "/operate/kubernetes/security/manage-rec-credentials/">}}) |
-| Lightweight Directory Access Protocol (LDAP) |  | [LDAP authentication]({{<relref "/operate/rs/security/access-control/ldap">}}) |  | [Enable LDAP]({{<relref "/operate/kubernetes/security/ldap/">}}) |
+| Role-based access control (RBAC) | [Role-based access control]({{<relref "/operate/rc/security/access-control/data-access-control/role-based-access-control">}}) | [Access control]({{<relref "/operate/rs/security/access-control">}}) | [Access control list]({{< relref "/operate/oss_and_stack/management/security/acl" >}}) | [REC credentials]({{<relref "/operate/kubernetes/security/authentication/manage-rec-credentials/">}}) |
+| Lightweight Directory Access Protocol (LDAP) |  | [LDAP authentication]({{<relref "/operate/rs/security/access-control/ldap">}}) |  | [Enable LDAP]({{<relref "/operate/kubernetes/security/authentication/ldap/">}}) |
 | Single sign-on (SSO) | [SAML SSO]({{< relref "/operate/rc/security/access-control/saml-sso" >}}) |  |  |  |
-| Self-signed certificates |  | [Certificates]({{<relref "/operate/rs/security/certificates">}}) | [Certificate configuration]({{< relref "/operate/oss_and_stack/management/security/encryption#certificate-configuration" >}}) | [REC certificates]({{<relref "operate/kubernetes/security/manage-rec-certificates/">}}) |
-| Internode encryption | [Encryption at rest]({{< relref "/operate/rc/security/encryption-at-rest" >}}) | [Internode encryption]({{<relref "/operate/rs/security/encryption/internode-encryption">}}) |  | [Enable internode encryption]({{<relref "operate/kubernetes/security/internode-encryption/">}}) |
+| Self-signed certificates |  | [Certificates]({{<relref "/operate/rs/security/certificates">}}) | [Certificate configuration]({{< relref "/operate/oss_and_stack/management/security/encryption#certificate-configuration" >}}) | [REC certificates]({{<relref "operate/kubernetes/security/certificates/manage-rec-certificates/">}}) |
+| Internode encryption | [Encryption at rest]({{< relref "/operate/rc/security/encryption-at-rest" >}}) | [Internode encryption]({{<relref "/operate/rs/security/encryption/internode-encryption">}}) |  | [Enable internode encryption]({{<relref "operate/kubernetes/security/certificates/internode-encryption/">}}) |
 | Auditing |  | [Audit events]({{<relref "/operate/rs/security/audit-events">}}) | [Keyspace notifications]({{< relref "/develop/pubsub/keyspace-notifications" >}}) |  |

content/operate/kubernetes/_index.md

@@ -67,10 +67,10 @@ Set up globally distributed [Active-Active databases]({{< relref "/operate/kuber
 
 Manage [secure connections]({{< relref "/operate/kubernetes/security" >}}) and access control for your Redis Enterprise deployment.
 
-- [Manage REC credentials]({{< relref "/operate/kubernetes/security/manage-rec-credentials" >}})
-- [Manage REC certificates]({{< relref "/operate/kubernetes/security/manage-rec-certificates" >}})
-- [Internode encryption]({{< relref "/operate/kubernetes/security/internode-encryption" >}})
-- [LDAP authentication]({{< relref "/operate/kubernetes/security/ldap" >}})
+- [Manage REC credentials]({{< relref "/operate/kubernetes/security/authentication/manage-rec-credentials" >}})
+- [Manage REC certificates]({{< relref "/operate/kubernetes/security/certificates/manage-rec-certificates" >}})
+- [Internode encryption]({{< relref "/operate/kubernetes/security/certificates/internode-encryption" >}})
+- [LDAP authentication]({{< relref "/operate/kubernetes/security/authentication/ldap" >}})
 
 ## Reference
 

content/operate/kubernetes/active-active/_index.md

@@ -72,7 +72,7 @@ For examples, see the [YAML examples]({{< relref "/operate/kubernetes/reference/
 
 The operator automates Active-Active certificate updates. When you update the proxy or syncer certificate secret on a participating cluster's REC, the operator detects the change and propagates the new certificate to the other participating clusters.
 
-For details, see [Manage REC certificates]({{< relref "/operate/kubernetes/security/manage-rec-certificates" >}}) and [cert-manager integration]({{< relref "/operate/kubernetes/security/cert-manager" >}}).
+For details, see [Manage REC certificates]({{< relref "/operate/kubernetes/security/certificates/manage-rec-certificates" >}}) and [cert-manager integration]({{< relref "/operate/kubernetes/security/certificates/cert-manager" >}}).
 
 ### Limitations
 

content/operate/kubernetes/active-active/create-aa-crdb-cli.md

@@ -69,7 +69,7 @@ You'll need to create DNS aliases to resolve your API hostname `<api-hostname>`,
   - Description: Combined with database name to create the Active-Active database hostname
   - Format: string
   - Example value: `-cluster.ijk.example.com`
-- [**REC admin credentials**]({{< relref "/operate/kubernetes/security/manage-rec-credentials" >}}) `<username> <password>`:
+- [**REC admin credentials**]({{< relref "/operate/kubernetes/security/authentication/manage-rec-credentials" >}}) `<username> <password>`:
   - Description: Admin username and password for the REC stored in a secret
   - Format: string
   - Example value: username: `user@example.com`, password: `something`

content/operate/kubernetes/active-active/create-reaadb.md

@@ -116,6 +116,8 @@ reaadb-boeing     active   Valid                        up
 
 In case of errors, review the REAADB custom resource events and the Redis Enterprise operator logs.
 
+To add tags to an Active-Active database and expose them as metric labels, see [Enrich database metrics with tags]({{< relref "/operate/kubernetes/re-databases/enrich-metrics-with-tags" >}}).
+
 ## Example values
 
 This article uses the example values listed below. You can also find them in the [YAML examples]({{< relref "/operate/kubernetes/reference/yaml/active-active" >}}) section.

content/operate/kubernetes/architecture/_index.md

@@ -84,25 +84,25 @@ See the [RedisEnterpriseDatabase (REDB) API Reference]({{<relref "/operate/kuber
 
 ## Security
 
-Redis Enterprise for Kubernetes uses [secrets](https://kubernetes.io/docs/concepts/configuration/secret/) to manage your cluster credentials, cluster certificates, and client certificates. You can configure [LDAP]({{<relref "/operate/kubernetes/security/ldap">}}) and [internode encryption]({{<relref "/operate/kubernetes/security/internode-encryption">}}) using the [RedisEnterpriseCluster (REC)](#redisenterprisecluster-rec) spec.
+Redis Enterprise for Kubernetes uses [secrets](https://kubernetes.io/docs/concepts/configuration/secret/) to manage your cluster credentials, cluster certificates, and client certificates. You can configure [LDAP]({{<relref "/operate/kubernetes/security/authentication/ldap">}}) and [internode encryption]({{<relref "/operate/kubernetes/security/certificates/internode-encryption">}}) using the [RedisEnterpriseCluster (REC)](#redisenterprisecluster-rec) spec.
 
 ### REC credentials
 
 Redis Enterprise for Kubernetes uses the [RedisEnterpriseCluster (REC)]({{<relref "/operate/kubernetes/reference/api/redis_enterprise_cluster_api">}}) [custom resource](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/) to create a Redis Enterprise cluster. During creation it generates random credentials for the operator to use. The credentials are saved in a Kubernetes (K8s) [secret](https://kubernetes.io/docs/concepts/configuration/secret/). The secret name defaults to the name of the cluster.
 
-See [Manage REC credentials]({{<relref "/operate/kubernetes/security/manage-rec-credentials">}}) for more details.
+See [Manage REC credentials]({{<relref "/operate/kubernetes/security/authentication/manage-rec-credentials">}}) for more details.
 
 ### REC certificates
 
 By default, Redis Enterprise Software for Kubernetes generates TLS certificates for the cluster during creation. These self-signed certificates are generated on the first node of each Redis Enterprise cluster (REC) and are copied to all other nodes in the cluster.
 
-See [Manage REC certificates]({{<relref "/operate/kubernetes/security/manage-rec-certificates">}}) for more details.
+See [Manage REC certificates]({{<relref "/operate/kubernetes/security/certificates/manage-rec-certificates">}}) for more details.
 
 ### Client certificates
 
 For each client certificate you want to use, you need to create a [Kubernetes secret](https://kubernetes.io/docs/concepts/configuration/secret/) to hold it. You can then reference that secret in your [Redis Enterprise database (REDB)](#redisenterprisedatabase-redb) custom resource.
 
-See [Add client certificates]({{<relref "/operate/kubernetes/security/add-client-certificates">}}) for more details.
+See [Add client certificates]({{<relref "/operate/kubernetes/security/certificates/add-client-certificates">}}) for more details.
 
 ## Storage
 

content/operate/kubernetes/re-clusters/connect-prometheus-operator.md

@@ -13,6 +13,8 @@ weight: 92
 
 To collect  metrics data from your databases and Redis Enterprise cluster (REC), you can connect your [Prometheus](https://prometheus.io/) server to an endpoint exposed on your REC. Redis Enterprise for Kubernetes creates a dedicated service to expose the `prometheus` port (8070) for data collection. A custom resource called `ServiceMonitor` allows the [Prometheus operator](https://github.com/prometheus-operator/prometheus-operator/tree/main/Documentation) to connect to this port and collect data from Redis Enterprise.
 
+To expose database tags as metric labels so you can filter and group metrics by attributes such as environment or team, see [Enrich database metrics with tags]({{< relref "/operate/kubernetes/re-databases/enrich-metrics-with-tags" >}}).
+
 ## Prerequisites
 
 Before connecting Redis Enterprise to Prometheus on your Kubernetes cluster, make sure you've done the following:

content/operate/kubernetes/re-databases/db-controller.md

@@ -98,6 +98,8 @@ To modify the database:
 
     When the status is `active`, the database is ready for use.
 
+To add tags to a database and expose them as metric labels, see [Enrich database metrics with tags]({{< relref "/operate/kubernetes/re-databases/enrich-metrics-with-tags" >}}).
+
 ## Delete a database
 
 The database exists as long as the custom resource exists.