diff --git a/content/operate/kubernetes/active-active/_index.md b/content/operate/kubernetes/active-active/_index.md index 285382330..dc77e649e 100644 --- a/content/operate/kubernetes/active-active/_index.md +++ b/content/operate/kubernetes/active-active/_index.md @@ -29,7 +29,7 @@ Versions 6.4.2-6 or later fully support the Active-Active controller. Some of th This setup method includes the following steps: -1. Gather REC credentials and [prepare participating clusters]({{< relref "/operate/kubernetes/active-active/prepare-clusters.md" >}}). +1. Gather REC credentials and [prepare participating clusters]({{< relref "/operate/kubernetes/active-active/prepare-clusters" >}}). 2. Create [`RedisEnterpriseRemoteCluster` (RERC)]({{< relref "/operate/kubernetes/active-active/create-reaadb#create-rerc" >}}) resources. 3. Create [`RedisEnterpriseActiveActiveDatabase` (REAADB)]({{< relref "/operate/kubernetes/active-active/create-reaadb#create-reaadb" >}}) resource. @@ -48,7 +48,7 @@ For versions 6.4.2 or earlier, this Active-Active setup method includes the foll [Active-Active]({{< relref "/operate/rs/databases/active-active/" >}}) databases give you read-and-write access to Redis Enterprise clusters (REC) in different Kubernetes clusters or namespaces. Active-Active deployments managed by the Redis Enterprise operator require two additional custom resources: Redis Enterprise Active-Active database (REAADB) and Redis Enterprise remote cluster (RERC). -To create an Active-Active Redis Enterprise deployment for Kubernetes with these new features, first [prepare participating clusters]({{< relref "/operate/kubernetes/active-active/prepare-clusters.md" >}}) then [create an Active-Active database]({{< relref "/operate/kubernetes/active-active/create-reaadb.md" >}}). +To create an Active-Active Redis Enterprise deployment for Kubernetes with these new features, first [prepare participating clusters]({{< relref "/operate/kubernetes/active-active/prepare-clusters" >}}) then [create an Active-Active database]({{< relref "/operate/kubernetes/active-active/create-reaadb" >}}). ### Preview versions diff --git a/content/operate/kubernetes/active-active/create-aa-crdb-cli.md b/content/operate/kubernetes/active-active/create-aa-crdb-cli.md index 92d50424b..c5e9864e9 100644 --- a/content/operate/kubernetes/active-active/create-aa-crdb-cli.md +++ b/content/operate/kubernetes/active-active/create-aa-crdb-cli.md @@ -10,7 +10,7 @@ description: This section shows how to set up an Active-Active Redis Enterprise linkTitle: Create Active-Active with crdb-cli weight: 99 --- -{{}} Versions 6.4.2 and later support the Active-Active database controller. This controller allows you to create Redis Enterprise Active-Active databases (REAADB) and Redis Enterprise remote clusters (RERC) with custom resources. We recommend using the [REAADB method for creating Active-Active databases]({{< relref "/operate/kubernetes/active-active/create-reaadb.md" >}}).{{}} +{{}} Versions 6.4.2 and later support the Active-Active database controller. This controller allows you to create Redis Enterprise Active-Active databases (REAADB) and Redis Enterprise remote clusters (RERC) with custom resources. We recommend using the [REAADB method for creating Active-Active databases]({{< relref "/operate/kubernetes/active-active/create-reaadb" >}}).{{}} On Kubernetes, Redis Enterprise [Active-Active]({{< relref "/operate/rs/databases/active-active/" >}}) databases provide read-and-write access to the same dataset from different Kubernetes clusters. For more general information about Active-Active, see the [Redis Enterprise Software docs]({{< relref "/operate/rs/databases/active-active/" >}}). @@ -26,9 +26,9 @@ This process consists of: Before creating Active-Active databases, you'll need admin access to two or more working Kubernetes clusters that each have: -- Routing for external access with an [ingress resources]({{< relref "/operate/kubernetes/networking/ingress.md" >}}) (or [route resources]({{< relref "/operate/kubernetes/networking/routes.md" >}}) on OpenShift). +- Routing for external access with an [ingress resources]({{< relref "/operate/kubernetes/networking/ingress" >}}) (or [route resources]({{< relref "/operate/kubernetes/networking/routes" >}}) on OpenShift). - A working [Redis Enterprise cluster (REC)]({{< relref "/operate/kubernetes/reference/redis_enterprise_cluster_api" >}}) with a unique name. -- Enough memory resources available for the database (see [hardware requirements]({{< relref "/operate/rs/installing-upgrading/install/plan-deployment/hardware-requirements.md" >}})). +- Enough memory resources available for the database (see [hardware requirements]({{< relref "/operate/rs/installing-upgrading/install/plan-deployment/hardware-requirements" >}})). {{}} The `activeActive` field and the `ingressOrRouteSpec` field cannot coexist in the same REC. If you configured your ingress via the `ingressOrRouteSpec` field in the REC, create your Active-Active database with the RedisEnterpriseActiveActiveDatabase (REAADB) custom resource.{{}} @@ -69,7 +69,7 @@ You'll need to create DNS aliases to resolve your 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.md" >}}) ` `: +- [**REC admin credentials**]({{< relref "/operate/kubernetes/security/manage-rec-credentials" >}}) ` `: - Description: Admin username and password for the REC stored in a secret - Format: string - Example value: username: `user@example.com`, password: `something` @@ -99,7 +99,7 @@ From inside your K8s cluster, edit your Redis Enterprise cluster (REC) resource ### Using ingress controller -1. If your cluster uses an [ingress controller]({{< relref "/operate/kubernetes/networking/ingress.md" >}}), add the following to the `spec` section of your REC resource file. +1. If your cluster uses an [ingress controller]({{< relref "/operate/kubernetes/networking/ingress" >}}), add the following to the `spec` section of your REC resource file. Nginx: @@ -146,7 +146,7 @@ HAproxy: #### If using Istio Gateway and VirtualService -No changes are required to the REC spec if you are using [Istio]({{< relref "/operate/kubernetes/networking/istio-ingress.md" >}}) in place of an ingress controller. The `activeActive` section added above creates ingress resources. The two custom resources used to configure Istio (Gateway and VirtualService) replace the need for ingress resources. +No changes are required to the REC spec if you are using [Istio]({{< relref "/operate/kubernetes/networking/istio-ingress" >}}) in place of an ingress controller. The `activeActive` section added above creates ingress resources. The two custom resources used to configure Istio (Gateway and VirtualService) replace the need for ingress resources. {{}} These custom resources are not controlled by the operator and will need to be configured and maintained manually. @@ -173,7 +173,7 @@ For each cluster, verify the VirtualService resource has two `- match:` blocks i 1. Make sure you have DNS aliases for each database that resolve your API hostname ``,``, `` to the route IP address. To avoid entering multiple DNS records, you can use a wildcard in your alias (such as `*.ijk.example.com`). -1. If your cluster uses [OpenShift routes]({{< relref "/operate/kubernetes/networking/routes.md" >}}), add the following to the `spec` section of your Redis Enterprise cluster (REC) resource file. +1. If your cluster uses [OpenShift routes]({{< relref "/operate/kubernetes/networking/routes" >}}), add the following to the `spec` section of your Redis Enterprise cluster (REC) resource file. ```sh activeActive: diff --git a/content/operate/kubernetes/active-active/create-reaadb.md b/content/operate/kubernetes/active-active/create-reaadb.md index 49011af45..15adbc893 100644 --- a/content/operate/kubernetes/active-active/create-reaadb.md +++ b/content/operate/kubernetes/active-active/create-reaadb.md @@ -16,18 +16,18 @@ weight: 30 To create an Active-Active database, make sure you've completed all the following steps and have gathered the information listed below each step. -1. Configure the [admission controller and ValidatingWebhook]({{< relref "/operate/kubernetes/deployment/quick-start.md#enable-the-admission-controller/" >}}). +1. Configure the [admission controller and ValidatingWebhook]({{< relref "/operate/kubernetes/deployment/quick-start#enable-the-admission-controller/" >}}). {{}}These are installed and enabled by default on clusters created via the OpenShift OperatorHub. {{}} -2. Create two or more [RedisEnterpriseCluster (REC) custom resources]({{< relref "/operate/kubernetes/deployment/quick-start#create-a-redis-enterprise-cluster-rec" >}}) with enough [memory resources]({{< relref "/operate/rs/installing-upgrading/install/plan-deployment/hardware-requirements.md" >}}). +2. Create two or more [RedisEnterpriseCluster (REC) custom resources]({{< relref "/operate/kubernetes/deployment/quick-start#create-a-redis-enterprise-cluster-rec" >}}) with enough [memory resources]({{< relref "/operate/rs/installing-upgrading/install/plan-deployment/hardware-requirements" >}}). * Name of each REC (``) * Namespace for each REC (``) -3. Configure the REC [`ingressOrRoutes` field]({{< relref "/operate/kubernetes/networking/ingressorroutespec.md" >}}) and [create DNS records]({{< relref "/operate/kubernetes/networking/ingressorroutespec#configure-dns/" >}}). +3. Configure the REC [`ingressOrRoutes` field]({{< relref "/operate/kubernetes/networking/ingressorroutespec" >}}) and [create DNS records]({{< relref "/operate/kubernetes/networking/ingressorroutespec#configure-dns/" >}}). * REC API hostname (`api--.`) * Database hostname suffix (`-db--.`) -4. [Prepare participating clusters]({{< relref "/operate/kubernetes/active-active/prepare-clusters.md" >}}) +4. [Prepare participating clusters]({{< relref "/operate/kubernetes/active-active/prepare-clusters" >}}) * RERC name (`) * RERC secret name (`redis-enterprise-`) diff --git a/content/operate/kubernetes/active-active/edit-clusters.md b/content/operate/kubernetes/active-active/edit-clusters.md index 995e707d4..680581dba 100644 --- a/content/operate/kubernetes/active-active/edit-clusters.md +++ b/content/operate/kubernetes/active-active/edit-clusters.md @@ -18,7 +18,7 @@ Use the following steps to add a participating cluster to an existing Redis Ente ### Prerequisites -To prepare the Redis Enterprise cluster (REC) to participate in an Active-Active database, perform the following tasks from [Prepare participating clusters]({{< relref "/operate/kubernetes/active-active/prepare-clusters.md" >}}): +To prepare the Redis Enterprise cluster (REC) to participate in an Active-Active database, perform the following tasks from [Prepare participating clusters]({{< relref "/operate/kubernetes/active-active/prepare-clusters" >}}): - Make sure the cluster meets the hardware and naming requirements. - Enable the Active-Active controllers. diff --git a/content/operate/kubernetes/active-active/global-db-secret.md b/content/operate/kubernetes/active-active/global-db-secret.md index 76d361a3c..fcac77dc4 100644 --- a/content/operate/kubernetes/active-active/global-db-secret.md +++ b/content/operate/kubernetes/active-active/global-db-secret.md @@ -16,7 +16,7 @@ weight: 50 One of the fields available for `globalConfigurations` is `databaseSecretName` which can point to a secret containing the database password. To set the database secret name and sync the data to all participating clusters, follow the steps below. -To edit other global configruations, see [global configuration]({{< relref "/operate/kubernetes/active-active/global-config.md" >}}) +To edit other global configruations, see [global configuration]({{< relref "/operate/kubernetes/active-active/global-config" >}}) 1. On an existing participating cluster, generate a YAML file containing the database secret with the database password. diff --git a/content/operate/kubernetes/active-active/prepare-clusters.md b/content/operate/kubernetes/active-active/prepare-clusters.md index a62bd3eb6..02bf7d59c 100644 --- a/content/operate/kubernetes/active-active/prepare-clusters.md +++ b/content/operate/kubernetes/active-active/prepare-clusters.md @@ -17,13 +17,13 @@ weight: 10 Before you prepare your clusters to participate in an Active-Active database, make sure you've completed all the following steps and have gathered the information listed below each step. -1. Configure the [admission controller and ValidatingWebhook]({{< relref "/operate/kubernetes/deployment/quick-start.md#enable-the-admission-controller/" >}}). +1. Configure the [admission controller and ValidatingWebhook]({{< relref "/operate/kubernetes/deployment/quick-start#enable-the-admission-controller/" >}}). -2. Create two or more [RedisEnterpriseCluster (REC) custom resources]({{< relref "/operate/kubernetes/deployment/quick-start#create-a-redis-enterprise-cluster-rec" >}}) with enough [memory resources]({{< relref "/operate/rs/installing-upgrading/install/plan-deployment/hardware-requirements.md" >}}). +2. Create two or more [RedisEnterpriseCluster (REC) custom resources]({{< relref "/operate/kubernetes/deployment/quick-start#create-a-redis-enterprise-cluster-rec" >}}) with enough [memory resources]({{< relref "/operate/rs/installing-upgrading/install/plan-deployment/hardware-requirements" >}}). * Name of each REC (``) * Namespace for each REC (``) -3. Configure the REC [`ingressOrRoutes` field]({{< relref "/operate/kubernetes/networking/ingressorroutespec.md" >}}) and [create DNS records]({{< relref "/operate/kubernetes/networking/ingressorroutespec#configure-dns/" >}}). +3. Configure the REC [`ingressOrRoutes` field]({{< relref "/operate/kubernetes/networking/ingressorroutespec" >}}) and [create DNS records]({{< relref "/operate/kubernetes/networking/ingressorroutespec#configure-dns/" >}}). * REC API hostname (`api--.`) * Database hostname suffix (`-db--.`) @@ -140,7 +140,7 @@ To communicate with other clusters, all participating clusters will need access ## Next steps -Now you are ready to [create your Redis Enterprise Active-Active database]({{< relref "/operate/kubernetes/active-active/create-reaadb.md" >}}). +Now you are ready to [create your Redis Enterprise Active-Active database]({{< relref "/operate/kubernetes/active-active/create-reaadb" >}}). ## Example values diff --git a/content/operate/kubernetes/architecture/_index.md b/content/operate/kubernetes/architecture/_index.md index 4a13f354b..c7fb95a5e 100644 --- a/content/operate/kubernetes/architecture/_index.md +++ b/content/operate/kubernetes/architecture/_index.md @@ -95,7 +95,7 @@ See [Manage REC credentials]({{}}) for more details. +See [Manage REC certificates]({{}}) for more details. ### Client certificates @@ -123,7 +123,7 @@ By default, Kubernetes doesn't allow you to access your Redis database from outs - Ingress controllers [HAProxy](https://haproxy-ingress.github.io/) and [NGINX](https://kubernetes.github.io/ingress-nginx/) require an `ingress` API resource. - [Istio](https://istio.io/latest/docs/setup/getting-started/) requires `Gateway` and `VirtualService` API resources. -- OpenShift uses [routes]({{< relref "/operate/kubernetes/networking/routes.md" >}}) to route external traffic. +- OpenShift uses [routes]({{< relref "/operate/kubernetes/networking/routes" >}}) to route external traffic. The [Active-Active databases](#active-active-databases) require one of above routing methods to be configured in the REC with the [ingressOrRouteSpec field]({{}}). diff --git a/content/operate/kubernetes/architecture/deployment-options.md b/content/operate/kubernetes/architecture/deployment-options.md index 536b2695c..dab7d66b5 100644 --- a/content/operate/kubernetes/architecture/deployment-options.md +++ b/content/operate/kubernetes/architecture/deployment-options.md @@ -20,13 +20,13 @@ The Redis Enterprise cluster (REC) custom resource must reside in the same names ## Single REC and single namespace (one-to-one) -The standard and simplest deployment deploys your Redis Enterprise databases (REDB) in the same namespace as the Redis Enterprise cluster (REC). No additional configuration is required for this, since there is no communication required to cross namespaces. See [Deploy Redis Enterprise for Kubernetes]({{< relref "/operate/kubernetes/deployment/quick-start.md" >}}). +The standard and simplest deployment deploys your Redis Enterprise databases (REDB) in the same namespace as the Redis Enterprise cluster (REC). No additional configuration is required for this, since there is no communication required to cross namespaces. See [Deploy Redis Enterprise for Kubernetes]({{< relref "/operate/kubernetes/deployment/quick-start" >}}). {{< image filename="/images/k8s/k8s-deploy-one-to-one.png" >}} ## Single REC and multiple namespaces (one-to-many) -Multiple Redis Enterprise databases (REDB) spread across multiple namespaces within the same K8s cluster can be associated with the same Redis Enterprise cluster (REC). See [Manage databases in multiple namespaces]({{< relref "/operate/kubernetes/re-clusters/multi-namespace.md" >}}) for more information. +Multiple Redis Enterprise databases (REDB) spread across multiple namespaces within the same K8s cluster can be associated with the same Redis Enterprise cluster (REC). See [Manage databases in multiple namespaces]({{< relref "/operate/kubernetes/re-clusters/multi-namespace" >}}) for more information. {{< image filename="/images/k8s/k8s-deploy-one-to-many.png" >}} @@ -36,7 +36,7 @@ A single Kubernetes cluster can contain multiple Redis Enterprise clusters (REC) You have the flexibility to create databases in separate namespaces, or in the same namespace as the REC, or combine any of the supported deployment options above. This configuration is geared towards use cases that require multiple Redis Enterprise clusters with greater isolation or different cluster configurations. -See [Manage databases in multiple namespaces]({{< relref "/operate/kubernetes/re-clusters/multi-namespace.md" >}}) for more information. +See [Manage databases in multiple namespaces]({{< relref "/operate/kubernetes/re-clusters/multi-namespace" >}}) for more information. {{< image filename="/images/k8s/k8s-deploy-many-to-many.png" >}} diff --git a/content/operate/kubernetes/deployment/container-images.md b/content/operate/kubernetes/deployment/container-images.md index 6f8ce71da..09a118578 100644 --- a/content/operate/kubernetes/deployment/container-images.md +++ b/content/operate/kubernetes/deployment/container-images.md @@ -126,7 +126,7 @@ require authentication. If you do need authentication, add a [pull secret](https The operator bundle contains the operator deployment and the reference to the operator image (`redislabs/operator`). To use a private container registry, you must change this image reference in your operator deployment file **before** you deploy the operator. If you apply this change to modify an existing operator deployment, the operator's pod will restart. -In the operator deployment file, 'containers:image' should point to the same repository and tag you used when [pushing]({{< relref "/operate/kubernetes/deployment/container-images.md#push-images-to-a-private-container-registry" >}}) to the private container registry: +In the operator deployment file, 'containers:image' should point to the same repository and tag you used when [pushing]({{< relref "/operate/kubernetes/deployment/container-images#push-images-to-a-private-container-registry" >}}) to the private container registry: ```sh ${PRIVATE_REPO}/redislabs/operator:${OPERATOR_VERSION} diff --git a/content/operate/kubernetes/deployment/helm.md b/content/operate/kubernetes/deployment/helm.md index f0b918ddd..5c6665dd7 100644 --- a/content/operate/kubernetes/deployment/helm.md +++ b/content/operate/kubernetes/deployment/helm.md @@ -16,7 +16,7 @@ Helm charts provide a simple way to install the Redis Enterprise for Kubernetes ## Prerequisites -- A [supported distribution]({{< relref "/operate/kubernetes/reference/supported_k8s_distributions.md" >}}) of Kubernetes. +- A [supported distribution]({{< relref "/operate/kubernetes/reference/supported_k8s_distributions" >}}) of Kubernetes. - At least three worker nodes. - [Kubernetes client (kubectl)](https://kubernetes.io/docs/tasks/tools/). - [Helm 3.10 or later](https://helm.sh/docs/intro/install/). diff --git a/content/operate/kubernetes/deployment/openshift/_index.md b/content/operate/kubernetes/deployment/openshift/_index.md index 68c872cbf..2505ffda2 100644 --- a/content/operate/kubernetes/deployment/openshift/_index.md +++ b/content/operate/kubernetes/deployment/openshift/_index.md @@ -27,13 +27,13 @@ workloads can use: ## For OpenShift via the OperatorHub -To [create a database on an OpenShift 4.x cluster via the OperatorHub]({{< relref "/operate/kubernetes/deployment/openshift/openshift-operatorhub" >}}) you only need to have the [OpenShift 4.x cluster installed](https://docs.openshift.com/container-platform/4.3/welcome/index.html) with at least three nodes that each meet the [minimum requirements for a development installation]({{< relref "/operate/rs/installing-upgrading/install/plan-deployment/hardware-requirements.md" >}}). +To [create a database on an OpenShift 4.x cluster via the OperatorHub]({{< relref "/operate/kubernetes/deployment/openshift/openshift-operatorhub" >}}) you only need to have the [OpenShift 4.x cluster installed](https://docs.openshift.com/container-platform/4.3/welcome/index.html) with at least three nodes that each meet the [minimum requirements for a development installation]({{< relref "/operate/rs/installing-upgrading/install/plan-deployment/hardware-requirements" >}}). ## For OpenShift via the CLI -To [create a database on an OpenShift cluster via the CLI]({{< relref "/operate/kubernetes/deployment/openshift/openshift-cli.md" >}}), you need: +To [create a database on an OpenShift cluster via the CLI]({{< relref "/operate/kubernetes/deployment/openshift/openshift-cli" >}}), you need: -1. An [OpenShift cluster installed](https://docs.openshift.com/container-platform/4.3/welcome/index.html) with at least three nodes that each meet the [minimum requirements for a development installation]({{< relref "/operate/rs/installing-upgrading/install/plan-deployment/hardware-requirements.md" >}}). +1. An [OpenShift cluster installed](https://docs.openshift.com/container-platform/4.3/welcome/index.html) with at least three nodes that each meet the [minimum requirements for a development installation]({{< relref "/operate/rs/installing-upgrading/install/plan-deployment/hardware-requirements" >}}). 1. The [kubectl package installed](https://kubernetes.io/docs/tasks/tools/install-kubectl/) at version 1.9 or higher 1. The [OpenShift cli installed](https://docs.openshift.com/container-platform/4.2/cli_reference/openshift_cli/getting-started-cli.html) diff --git a/content/operate/kubernetes/deployment/openshift/openshift-cli.md b/content/operate/kubernetes/deployment/openshift/openshift-cli.md index 16b8f0385..061dffc1c 100644 --- a/content/operate/kubernetes/deployment/openshift/openshift-cli.md +++ b/content/operate/kubernetes/deployment/openshift/openshift-cli.md @@ -114,7 +114,7 @@ Each Redis Enterprise cluster requires at least 3 nodes. Single-node RECs are no ## Configure the admission controller -{{< embed-md "k8s-admission-webhook-cert.md" >}} +{{< embed-md "k8s-admission-webhook-cert" >}} ### Limit the webhook to relevant namespaces @@ -188,7 +188,7 @@ The operator uses the instructions in the Redis Enterprise database (REDB) custo 1. Create a `RedisEnterpriseDatabase` custom resource. - This example creates a test database. For production databases, see [create a database]({{< relref "/operate/kubernetes/re-databases/db-controller.md#create-a-database" >}}) and [RedisEnterpriseDatabase API reference]({{< relref "/operate/kubernetes/reference/redis_enterprise_database_api" >}}). + This example creates a test database. For production databases, see [create a database]({{< relref "/operate/kubernetes/re-databases/db-controller#create-a-database" >}}) and [RedisEnterpriseDatabase API reference]({{< relref "/operate/kubernetes/reference/redis_enterprise_database_api" >}}). ```sh cat << EOF > /tmp/redis-enterprise-database.yml diff --git a/content/operate/kubernetes/deployment/quick-start.md b/content/operate/kubernetes/deployment/quick-start.md index 681ec095c..fb37c4b76 100644 --- a/content/operate/kubernetes/deployment/quick-start.md +++ b/content/operate/kubernetes/deployment/quick-start.md @@ -17,13 +17,13 @@ To deploy Redis Enterprise Software for Kubernetes and start your Redis Enterpri - Apply the operator bundle and verify it's running. - Create a Redis Enterprise cluster (REC). -This guide works with most supported Kubernetes distributions. If you're using OpenShift, see [Redis Enterprise on OpenShift]({{< relref "/operate/kubernetes/deployment/openshift" >}}). For details on what is currently supported, see [supported distributions]({{< relref "/operate/kubernetes/reference/supported_k8s_distributions.md" >}}). +This guide works with most supported Kubernetes distributions. If you're using OpenShift, see [Redis Enterprise on OpenShift]({{< relref "/operate/kubernetes/deployment/openshift" >}}). For details on what is currently supported, see [supported distributions]({{< relref "/operate/kubernetes/reference/supported_k8s_distributions" >}}). ## Prerequisites To deploy Redis Enterprise for Kubernetes, you'll need: -- Kubernetes cluster in a [supported distribution]({{< relref "/operate/kubernetes/reference/supported_k8s_distributions.md" >}}) +- Kubernetes cluster in a [supported distribution]({{< relref "/operate/kubernetes/reference/supported_k8s_distributions" >}}) - minimum of three worker nodes - Kubernetes client (kubectl) - access to DockerHub, RedHat Container Catalog, or a private repository that can hold the required images. @@ -51,7 +51,7 @@ You can use an existing namespace as long as it does not contain any existing Re ## Install the operator -Redis Enterprise for Kubernetes bundle is published as a container image. A list of required images is available in the [release notes]({{< relref "/operate/kubernetes/release-notes/_index.md" >}}) for each version. +Redis Enterprise for Kubernetes bundle is published as a container image. A list of required images is available in the [release notes]({{< relref "/operate/kubernetes/release-notes/_index" >}}) for each version. The operator [definition and reference materials](https://github.com/RedisLabs/redis-enterprise-k8s-docs) are available on GitHub. The operator definitions are [packaged as a single generic YAML file](https://github.com/RedisLabs/redis-enterprise-k8s-docs/blob/master/bundle.yaml). @@ -149,7 +149,7 @@ The REC name (`my-rec` in this example) cannot be changed after cluster creation Each cluster must have at least 3 nodes. Single-node RECs are not supported. {{}} - See the [Redis Enterprise hardware requirements]({{< relref "/operate/rs/installing-upgrading/install/plan-deployment/hardware-requirements.md" >}}) for more information on sizing Redis Enterprise node resource requests. + See the [Redis Enterprise hardware requirements]({{< relref "/operate/rs/installing-upgrading/install/plan-deployment/hardware-requirements" >}}) for more information on sizing Redis Enterprise node resource requests. 1. Apply your custom resource file in the same namespace as `my-rec.yaml`. @@ -196,7 +196,7 @@ The admission controller dynamically validates REDB resources configured by the As part of the REC creation process, the operator stores the admission controller certificate in a Kubernetes secret called `admission-tls`. You may have to wait a few minutes after creating your REC to see the secret has been created. -{{< embed-md "k8s-admission-webhook-cert.md" >}} +{{< embed-md "k8s-admission-webhook-cert" >}} ### Limit the webhook to the relevant namespaces {#webhook} @@ -257,4 +257,4 @@ The operator bundle includes a webhook file. The webhook will intercept requests You can create multiple databases within the same namespace as your REC or in other namespaces. -See [manage Redis Enterprise databases for Kubernetes]({{< relref "/operate/kubernetes/re-databases/db-controller.md" >}}) to create a new REDB. +See [manage Redis Enterprise databases for Kubernetes]({{< relref "/operate/kubernetes/re-databases/db-controller" >}}) to create a new REDB. diff --git a/content/operate/kubernetes/networking/_index.md b/content/operate/kubernetes/networking/_index.md index 66da195c6..02a9a5999 100644 --- a/content/operate/kubernetes/networking/_index.md +++ b/content/operate/kubernetes/networking/_index.md @@ -15,7 +15,7 @@ Redis Enterprise for Kubernetes supports several ways to route external traffic - Ingress controllers [HAProxy](https://haproxy-ingress.github.io/) and [NGINX](https://kubernetes.github.io/ingress-nginx/) require an `ingress` API resource. - [Istio](https://istio.io/latest/docs/setup/getting-started/) requires `Gateway` and `VirtualService` API resources. -- OpenShift uses [routes]({{< relref "/operate/kubernetes/networking/routes.md" >}}) to route external traffic. +- OpenShift uses [routes]({{< relref "/operate/kubernetes/networking/routes" >}}) to route external traffic. - The RedisEnterpriseActiveActiveDatabase (REAADB) requires any of the above routing methods to be configured in the RedisEnterpriseCluster (REC) with the `ingressOrRouteSpec` field. ## External routing using Redis Enterprise for Kubernetes @@ -26,13 +26,13 @@ Redis Enterprise supports three [types of services](https://kubernetes.io/docs/c By default, the operator creates a `ClusterIP` type service, which exposes a cluster-internal IP and that can only be accessed from within the K8s cluster. For requests to be routed from outside the K8s cluster, you need an [Ingress](https://kubernetes.io/docs/concepts/services-networking/ingress/) (or [route](https://docs.openshift.com/container-platform/4.12/networking/routes/route-configuration.html) if you are using OpenShift). See [kubernetes.io](https://kubernetes.io/docs/) for more details on [Ingress](https://kubernetes.io/docs/concepts/services-networking/ingress/) and [Ingress controllers](https://kubernetes.io/docs/concepts/services-networking/ingress-controllers/). -* To use NGINX or HAProxy Ingress controllers, see [Ingress routing]({{< relref "/operate/kubernetes/networking/ingress.md" >}}). -* To use OpenShift routes, see [OpenShift routes]({{< relref "/operate/kubernetes/networking/routes.md" >}}). -* To use Istio as an Ingress controller, see [Istio Ingress routing]({{< relref "/operate/kubernetes/networking/istio-ingress.md" >}}) +* To use NGINX or HAProxy Ingress controllers, see [Ingress routing]({{< relref "/operate/kubernetes/networking/ingress" >}}). +* To use OpenShift routes, see [OpenShift routes]({{< relref "/operate/kubernetes/networking/routes" >}}). +* To use Istio as an Ingress controller, see [Istio Ingress routing]({{< relref "/operate/kubernetes/networking/istio-ingress" >}}) ## `ingressOrRouteSpec` for Active-Active databases -Versions 6.4.2 or later of Redis Enterprise for Kubernetes include a feature for ingress configuration. The `ingressOrRouteSpec` field is available in the RedisEnterpriseCluster spec to automatically create an Ingress (or route) for the API service and databases (REAADB) on that REC. See [REC external routing]({{< relref "/operate/kubernetes/networking/ingressorroutespec.md" >}}) for more details. +Versions 6.4.2 or later of Redis Enterprise for Kubernetes include a feature for ingress configuration. The `ingressOrRouteSpec` field is available in the RedisEnterpriseCluster spec to automatically create an Ingress (or route) for the API service and databases (REAADB) on that REC. See [REC external routing]({{< relref "/operate/kubernetes/networking/ingressorroutespec" >}}) for more details. This feature only supports automatic Ingress creation for Active-Active databases created and managed with the RedisEnterpriseActiveActiveDatabase (REAADB) custom resource. Use with the standard Redis Enterprise database (REDB) is not currently supported. diff --git a/content/operate/kubernetes/networking/ingress.md b/content/operate/kubernetes/networking/ingress.md index 58e3acb1a..d629e4d6f 100644 --- a/content/operate/kubernetes/networking/ingress.md +++ b/content/operate/kubernetes/networking/ingress.md @@ -20,7 +20,7 @@ Before creating an Ingress, you'll need: - [Ingress-NGINX Controller](https://kubernetes.github.io/ingress-nginx/deploy/) - Be sure to use the `kubernetes/ingress-nginx` controller and NOT the `nginxinc/kubernetes-ingress` controller. - [HAProxy Ingress](https://haproxy-ingress.github.io/docs/getting-started/) - - To use Istio for your Ingress resources, see [Configure Istio for external routing]({{< relref "/operate/kubernetes/networking/istio-ingress.md" >}}) + - To use Istio for your Ingress resources, see [Configure Istio for external routing]({{< relref "/operate/kubernetes/networking/istio-ingress" >}}) {{}}Make sure your Ingress controller has `ssl-passthrough`enabled. This is enabled by default for HAProxy, but disabled by default for NGINX. See the [NGINX User Guide](https://kubernetes.github.io/ingress-nginx/user-guide/tls/#ssl-passthrough) for details. {{}} diff --git a/content/operate/kubernetes/networking/ingressorroutespec.md b/content/operate/kubernetes/networking/ingressorroutespec.md index 58d1f6614..3aa48bd21 100644 --- a/content/operate/kubernetes/networking/ingressorroutespec.md +++ b/content/operate/kubernetes/networking/ingressorroutespec.md @@ -18,7 +18,7 @@ Redis Enterprise for Kubernetes supports the Ingress controllers below: * [NGINX](https://kubernetes.github.io/ingress-nginx/) * [Istio](https://istio.io/latest/docs/setup/getting-started/) -OpenShift users can use [routes]({{< relref "/operate/kubernetes/networking/routes.md" >}}) instead of an Ingress. +OpenShift users can use [routes]({{< relref "/operate/kubernetes/networking/routes" >}}) instead of an Ingress. Install your chosen Ingress controller, making sure `ssl-passthrough` is enabled. `ssl-passthrough` is turned off by default for NGINX but enabled by default for HAProxy. diff --git a/content/operate/kubernetes/networking/istio-ingress.md b/content/operate/kubernetes/networking/istio-ingress.md index 3854425c7..129fbf3e7 100644 --- a/content/operate/kubernetes/networking/istio-ingress.md +++ b/content/operate/kubernetes/networking/istio-ingress.md @@ -148,10 +148,10 @@ To configure Istio to work with the Redis Kubernetes operator, we will use two c redis-vs ["redis-gateway"] ["*.istio.k8s.my.example.com"] 3h33m ``` -1. [Deploy the operator]({{< relref "/operate/kubernetes/deployment/quick-start.md" >}}), Redis Enterprise Cluster (REC), and Redis Enterprise Database (REDB) on the same namespace as the gateway and virtual service. +1. [Deploy the operator]({{< relref "/operate/kubernetes/deployment/quick-start" >}}), Redis Enterprise Cluster (REC), and Redis Enterprise Database (REDB) on the same namespace as the gateway and virtual service. ## Test your external access to the database -To [test your external access]({{< relref "/operate/kubernetes/networking/ingress.md" >}}) to the database, you need a client that supports [TLS](https://en.wikipedia.org/wiki/Transport_Layer_Security) and [SNI](https://en.wikipedia.org/wiki/Server_Name_Indication). +To [test your external access]({{< relref "/operate/kubernetes/networking/ingress" >}}) to the database, you need a client that supports [TLS](https://en.wikipedia.org/wiki/Transport_Layer_Security) and [SNI](https://en.wikipedia.org/wiki/Server_Name_Indication). See [Test your access with Openssl]({{< relref "/operate/kubernetes/networking/ingress#test-your-access-with-openssl" >}}) or [Test your access with Python]({{< relref "/operate/kubernetes/networking/ingress#test-your-access-with-python" >}}) for more info. diff --git a/content/operate/kubernetes/re-clusters/auto-tiering.md b/content/operate/kubernetes/re-clusters/auto-tiering.md index 1c1b4fe4e..ef313e968 100644 --- a/content/operate/kubernetes/re-clusters/auto-tiering.md +++ b/content/operate/kubernetes/re-clusters/auto-tiering.md @@ -24,7 +24,7 @@ Before creating your Redis clusters or databases, these SSDs must be: - formatted and mounted on the nodes that will run Redis Enterprise pods - dedicated to Auto Tiering and not shared with other parts of the database, (e.g. durability, binaries) - [provisioned as local persistent volumes](https://kubernetes.io/docs/concepts/storage/volumes/#local) - - You can use a [local volume provisioner](https://github.com/kubernetes-sigs/sig-storage-local-static-provisioner/blob/master/README.md) to do this [dynamically](https://kubernetes.io/docs/concepts/storage/persistent-volumes/#dynamic) + - You can use a [local volume provisioner](https://github.com/kubernetes-sigs/sig-storage-local-static-provisioner/blob/master/README) to do this [dynamically](https://kubernetes.io/docs/concepts/storage/persistent-volumes/#dynamic) - a [StorageClass](https://kubernetes.io/docs/concepts/storage/storage-classes/#local) resource with a unique name For more information on node storage, see [Node persistent and ephemeral storage]({{< relref "/operate/rs/installing-upgrading/install/plan-deployment/persistent-ephemeral-storage" >}}). diff --git a/content/operate/kubernetes/re-clusters/cluster-recovery.md b/content/operate/kubernetes/re-clusters/cluster-recovery.md index 29c49af4d..8e9f5c676 100644 --- a/content/operate/kubernetes/re-clusters/cluster-recovery.md +++ b/content/operate/kubernetes/re-clusters/cluster-recovery.md @@ -26,7 +26,7 @@ The Redis Enterprise for Kubernetes automates these recovery steps: ## Prerequisites -- For cluster recovery, the cluster must be [deployed with persistence]({{< relref "/operate/kubernetes/recommendations/persistent-volumes.md" >}}). +- For cluster recovery, the cluster must be [deployed with persistence]({{< relref "/operate/kubernetes/recommendations/persistent-volumes" >}}). ## Recover a cluster @@ -45,4 +45,4 @@ The Redis Enterprise for Kubernetes automates these recovery steps: watch "kubectl describe rec | grep State" ``` -1. To recover the database, see [Recover a failed database]({{< relref "/operate/rs/databases/recover.md" >}}). \ No newline at end of file +1. To recover the database, see [Recover a failed database]({{< relref "/operate/rs/databases/recover" >}}). \ No newline at end of file diff --git a/content/operate/kubernetes/re-clusters/connect-prometheus-operator.md b/content/operate/kubernetes/re-clusters/connect-prometheus-operator.md index 430696812..784db552e 100644 --- a/content/operate/kubernetes/re-clusters/connect-prometheus-operator.md +++ b/content/operate/kubernetes/re-clusters/connect-prometheus-operator.md @@ -17,8 +17,8 @@ To collect metrics data from your databases and Redis Enterprise cluster (REC), Before connecting Redis Enterprise to Prometheus on your Kubernetes cluster, make sure you've done the following: -- [Deploy Redis Enterprise for Kubernetes]({{< relref "/operate/kubernetes/deployment/quick-start.md" >}}) (version 6.2.10-4 or newer) -- [Deploy the Prometheus operator](https://github.com/prometheus-operator/prometheus-operator/blob/main/Documentation/user-guides/getting-started.md) (version 0.19.0 or newer) +- [Deploy Redis Enterprise for Kubernetes]({{< relref "/operate/kubernetes/deployment/quick-start" >}}) (version 6.2.10-4 or newer) +- [Deploy the Prometheus operator](https://github.com/prometheus-operator/prometheus-operator/blob/main/Documentation/user-guides/getting-started) (version 0.19.0 or newer) - [Create a Redis Enterprise cluster]({{< relref "/operate/kubernetes/deployment/quick-start#create-a-redis-enterprise-cluster-rec" >}}) ## Create a `ServiceMonitor` custom resource @@ -34,7 +34,7 @@ You'll need to configure the following fields to connect Prometheus to Redis Ent | `spec.selector` | `matchLabels` | REC service label (`app: redis.io/service=prom-metrics`) | Apply the file in the same namespace as your Redis Enterprise cluster (REC). - {{}}If Redis Enterprise and Prometheus are deployed in different namespaces, you'll also need to add the [`serviceMonitorNamespaceSelector`](https://github.com/prometheus-operator/prometheus-operator/blob/main/Documentation/api.md#namespaceselector) field to your Prometheus resource. See the [Prometheus operator documentation](https://github.com/prometheus-operator/prometheus-operator/blob/main/Documentation/user-guides/getting-started.md#related-resources) for more details on cross-namespace `ServiceMonitor` configuration.{{}} + {{}}If Redis Enterprise and Prometheus are deployed in different namespaces, you'll also need to add the [`serviceMonitorNamespaceSelector`](https://github.com/prometheus-operator/prometheus-operator/blob/main/Documentation/api#namespaceselector) field to your Prometheus resource. See the [Prometheus operator documentation](https://github.com/prometheus-operator/prometheus-operator/blob/main/Documentation/user-guides/getting-started#related-resources) for more details on cross-namespace `ServiceMonitor` configuration.{{}} ```YAML @@ -57,15 +57,15 @@ spec: redis.io/service: prom-metrics ``` -For more info about configuring the `ServiceMonitor` resource, see the [`ServiceMonitorSpec` API documentation](https://github.com/prometheus-operator/prometheus-operator/blob/main/Documentation/api.md#servicemonitorspec). +For more info about configuring the `ServiceMonitor` resource, see the [`ServiceMonitorSpec` API documentation](https://github.com/prometheus-operator/prometheus-operator/blob/main/Documentation/api#servicemonitorspec). ## More info - github.com/prometheus-operator - - [Getting started](https://github.com/prometheus-operator/prometheus-operator/blob/main/Documentation/user-guides/getting-started.md) - - [Running exporters](https://github.com/prometheus-operator/prometheus-operator/blob/main/Documentation/user-guides/running-exporters.md) - - [Related resources](https://github.com/prometheus-operator/prometheus-operator/blob/main/Documentation/user-guides/getting-started.md#related-resources) - - [Troubleshooting ServiceMonitor changes](https://github.com/prometheus-operator/prometheus-operator/blob/main/Documentation/troubleshooting.md) + - [Getting started](https://github.com/prometheus-operator/prometheus-operator/blob/main/Documentation/user-guides/getting-started) + - [Running exporters](https://github.com/prometheus-operator/prometheus-operator/blob/main/Documentation/user-guides/running-exporters) + - [Related resources](https://github.com/prometheus-operator/prometheus-operator/blob/main/Documentation/user-guides/getting-started#related-resources) + - [Troubleshooting ServiceMonitor changes](https://github.com/prometheus-operator/prometheus-operator/blob/main/Documentation/troubleshooting) - redis.io/docs - [Metrics in Prometheus]({{< relref "/integrate/prometheus-with-redis-enterprise/prometheus-metrics-definitions" >}}) - [Monitoring and metrics]({{< relref "/operate/rs/monitoring/" >}}) diff --git a/content/operate/kubernetes/re-clusters/multi-namespace.md b/content/operate/kubernetes/re-clusters/multi-namespace.md index 4efea9e94..78d5273c6 100644 --- a/content/operate/kubernetes/re-clusters/multi-namespace.md +++ b/content/operate/kubernetes/re-clusters/multi-namespace.md @@ -14,7 +14,7 @@ weight: 17 Multiple Redis Enterprise database resources (REDBs) can be associated with a single Redis Enterprise cluster resource (REC) even if they reside in different namespaces. -To learn more about designing a multi-namespace Redis Enterprise cluster, see [flexible deployment options]({{< relref "/operate/kubernetes/architecture/deployment-options.md" >}}). +To learn more about designing a multi-namespace Redis Enterprise cluster, see [flexible deployment options]({{< relref "/operate/kubernetes/architecture/deployment-options" >}}). {{}} Multi-namespace installations now support Active-Active databases (REAADB) with certain configuration requirements. For details, see [Multi-namespace Active-Active databases](#multi-namespace-active-active-databases). @@ -22,13 +22,13 @@ Multi-namespace installations now support Active-Active databases (REAADB) with ## Prerequisites -Before configuring a multi-namespace deployment, you must have a running [Redis Enterprise cluster (REC)]({{< relref "/operate/kubernetes/deployment/quick-start.md" >}}). See more information in the [deployment]({{< relref "/operate/kubernetes/deployment/" >}}) section. +Before configuring a multi-namespace deployment, you must have a running [Redis Enterprise cluster (REC)]({{< relref "/operate/kubernetes/deployment/quick-start" >}}). See more information in the [deployment]({{< relref "/operate/kubernetes/deployment/" >}}) section. ## Create role and role binding for managed namespaces Both the operator and the RedisEnterpriseCluster (REC) resource need access to each namespace the REC will manage. For each **managed** namespace, create a `role.yaml` and `role_binding.yaml` file within the managed namespace, as shown in the examples below. -{{}}These will need to be reapplied each time you [upgrade]({{< relref "/operate/kubernetes/upgrade/upgrade-redis-cluster.md" >}}). {{}} +{{}}These will need to be reapplied each time you [upgrade]({{< relref "/operate/kubernetes/upgrade/upgrade-redis-cluster" >}}). {{}} Replace `` with the namespace the REC resides in. Replace `` with your own value (defaults to the REC name). @@ -196,7 +196,7 @@ You can also deploy `RedisEnterpriseActiveActiveDatabase` (REAADB) objects in co To do this: 1. Configure each participating cluster’s operator to watch the relevant consumer namespace. See [multi-namespace operator setup](#update-redis-enterprise-operator-configmap). -2. Ensure all Active-Active prerequisites are met as described in [Configure Active-Active]({{}}). +2. Ensure all Active-Active prerequisites are met as described in [Configure Active-Active]({{}}). 3. In your REAADB custom resource, specify the target consumer namespace using `metadata.namespace`. For each participating cluster, use the `namespace` field under `spec.participatingClusters` to indicate the namespace where the REAADB should be deployed. 4. If you are using a [global database secret]({{}}), deploy the secret in each consumer namespace. diff --git a/content/operate/kubernetes/re-databases/db-controller.md b/content/operate/kubernetes/re-databases/db-controller.md index 7bd8f96a9..e80e2d933 100644 --- a/content/operate/kubernetes/re-databases/db-controller.md +++ b/content/operate/kubernetes/re-databases/db-controller.md @@ -32,7 +32,7 @@ If the database [custom resource is deleted]({{< relref "/operate/kubernetes/re- Databases in multiple namespaces can be managed by the same operator. To learn more, see [Manage databases in multiple namespaces]({{}}). -To learn more about designing a multi-namespace Redis Enterprise cluster, see [flexible deployment options]({{< relref "/operate/kubernetes/architecture/deployment-options.md" >}}). +To learn more about designing a multi-namespace Redis Enterprise cluster, see [flexible deployment options]({{< relref "/operate/kubernetes/architecture/deployment-options" >}}). ## Create a database @@ -84,7 +84,7 @@ To modify the database: ``` 1. Change the specification (only properties in `spec` section) and save the changes. - For more details, see [RedisEnterpriseDatabaseSpec](https://github.com/RedisLabs/redis-enterprise-k8s-docs/blob/master/redis_enterprise_database_api.md#redisenterprisedatabasespec) or [Options for Redis Enterprise databases]({{< relref "/operate/kubernetes/reference/redis_enterprise_database_api" >}}). + For more details, see [RedisEnterpriseDatabaseSpec](https://github.com/RedisLabs/redis-enterprise-k8s-docs/blob/master/redis_enterprise_database_api#redisenterprisedatabasespec) or [Options for Redis Enterprise databases]({{< relref "/operate/kubernetes/reference/redis_enterprise_database_api" >}}). 1. Monitor the status to see when the changes take effect: @@ -118,7 +118,7 @@ Connection information for the database is stored in a Kubernetes [secret](https The name of that secret is stored in the database custom resource. {{}} -Use these steps to connect to your database from within your K8s cluster. To access your database from outside the K8s cluster, set up the [Ingress]({{< relref "/operate/kubernetes/networking/ingress.md" >}}) controller or use OpenShift routes. +Use these steps to connect to your database from within your K8s cluster. To access your database from outside the K8s cluster, set up the [Ingress]({{< relref "/operate/kubernetes/networking/ingress" >}}) controller or use OpenShift routes. {{}} 1. Retrieve the secret name. diff --git a/content/operate/kubernetes/recommendations/node-resources.md b/content/operate/kubernetes/recommendations/node-resources.md index 2f7fdbea9..090a1f421 100644 --- a/content/operate/kubernetes/recommendations/node-resources.md +++ b/content/operate/kubernetes/recommendations/node-resources.md @@ -42,7 +42,7 @@ For more information about monitoring node conditions, see [Node conditions](htt Kubernetes uses the `ResourceQuota` object to limit resource consumption per namespace. This lets you limit the number of objects created by a namespace or the amount of compute resources consumed by a namespace. -The resource settings for Redis Enterprise for Kubernetes are defined in the `operator.yaml` and the [`RedisEnterpriseCluster`](https://github.com/RedisLabs/redis-enterprise-k8s-docs/blob/master/redis_enterprise_cluster_api.md#redisenterpriseclusterspec) custom resource. +The resource settings for Redis Enterprise for Kubernetes are defined in the `operator.yaml` and the [`RedisEnterpriseCluster`](https://github.com/RedisLabs/redis-enterprise-k8s-docs/blob/master/redis_enterprise_cluster_api#redisenterpriseclusterspec) custom resource. The following settings are the minimum workloads for the operator to function. diff --git a/content/operate/kubernetes/recommendations/persistent-volumes.md b/content/operate/kubernetes/recommendations/persistent-volumes.md index e7fec0eb7..92c2739db 100644 --- a/content/operate/kubernetes/recommendations/persistent-volumes.md +++ b/content/operate/kubernetes/recommendations/persistent-volumes.md @@ -44,7 +44,7 @@ The REC deployment files in the [Kubernetes documentation](https://github.com/Re omitted, operator allocates five times (5x) the amount of memory (RAM) defined for nodes (see example below), which is the recommended persistent storage size as described in the [Hardware -requirements]({{< relref "/operate/rs/installing-upgrading/install/plan-deployment/hardware-requirements.md" >}}) article. +requirements]({{< relref "/operate/rs/installing-upgrading/install/plan-deployment/hardware-requirements" >}}) article. To explicitly specify the persistent storage size, use the *volumeSize* property as described in the example above. diff --git a/content/operate/kubernetes/recommendations/sizing-on-kubernetes.md b/content/operate/kubernetes/recommendations/sizing-on-kubernetes.md index 627591125..156418f26 100644 --- a/content/operate/kubernetes/recommendations/sizing-on-kubernetes.md +++ b/content/operate/kubernetes/recommendations/sizing-on-kubernetes.md @@ -14,7 +14,7 @@ The following article reviews the mechanism and methods available for sizing and scaling a Redis Enterprise cluster deployment. For minimum and recommended sizing, always follow the sizing guidelines -detailed in the [Redis Enterprise hardware requirements]({{< relref "/operate/rs/installing-upgrading/install/plan-deployment/hardware-requirements.md" >}}). +detailed in the [Redis Enterprise hardware requirements]({{< relref "/operate/rs/installing-upgrading/install/plan-deployment/hardware-requirements" >}}). ## Sizing and scaling cluster nodes @@ -114,7 +114,7 @@ Then, apply the file by running: {{< warning >}} When adjusting compute resources, make sure the ratio of persistent volume size and the new memory size are in accordance to the [Hardware -requirements]({{< relref "/operate/rs/installing-upgrading/install/plan-deployment/hardware-requirements.md" >}}). +requirements]({{< relref "/operate/rs/installing-upgrading/install/plan-deployment/hardware-requirements" >}}). Persistent volume claims can be expanded, but not reduced after creation. See [Expand PersistentVolumeClaim (PVC)]({{}}) for details. {{< /warning >}} diff --git a/content/operate/kubernetes/reference/kubernetes-api-reference-frontmatter.patch b/content/operate/kubernetes/reference/kubernetes-api-reference-frontmatter.patch index 9aa97fbba..bc502017a 100644 --- a/content/operate/kubernetes/reference/kubernetes-api-reference-frontmatter.patch +++ b/content/operate/kubernetes/reference/kubernetes-api-reference-frontmatter.patch @@ -1,7 +1,7 @@ -diff --git a/content/operate/kubernetes/reference/redis_enterprise_active_active_database_api.md b/content/operate/kubernetes/reference/redis_enterprise_active_active_database_api.md +diff --git a/content/operate/kubernetes/reference/redis_enterprise_active_active_database_api b/content/operate/kubernetes/reference/redis_enterprise_active_active_database_api index 01e82b1b..cacaa46c 100644 ---- a/content/operate/kubernetes/reference/redis_enterprise_active_active_database_api.md -+++ b/content/operate/kubernetes/reference/redis_enterprise_active_active_database_api.md +--- a/content/operate/kubernetes/reference/redis_enterprise_active_active_database_api ++++ b/content/operate/kubernetes/reference/redis_enterprise_active_active_database_api @@ -5,7 +5,7 @@ categories: - docs - operate @@ -11,10 +11,10 @@ index 01e82b1b..cacaa46c 100644 weight: 30 --- -diff --git a/content/operate/kubernetes/reference/redis_enterprise_cluster_api.md b/content/operate/kubernetes/reference/redis_enterprise_cluster_api.md +diff --git a/content/operate/kubernetes/reference/redis_enterprise_cluster_api b/content/operate/kubernetes/reference/redis_enterprise_cluster_api index 970ba528..6afe4c50 100644 ---- a/content/operate/kubernetes/reference/redis_enterprise_cluster_api.md -+++ b/content/operate/kubernetes/reference/redis_enterprise_cluster_api.md +--- a/content/operate/kubernetes/reference/redis_enterprise_cluster_api ++++ b/content/operate/kubernetes/reference/redis_enterprise_cluster_api @@ -5,8 +5,9 @@ categories: - docs - operate @@ -25,10 +25,10 @@ index 970ba528..6afe4c50 100644 --- apiVersion: -diff --git a/content/operate/kubernetes/reference/redis_enterprise_database_api.md b/content/operate/kubernetes/reference/redis_enterprise_database_api.md +diff --git a/content/operate/kubernetes/reference/redis_enterprise_database_api b/content/operate/kubernetes/reference/redis_enterprise_database_api index f925ce44..ea21766e 100644 ---- a/content/operate/kubernetes/reference/redis_enterprise_database_api.md -+++ b/content/operate/kubernetes/reference/redis_enterprise_database_api.md +--- a/content/operate/kubernetes/reference/redis_enterprise_database_api ++++ b/content/operate/kubernetes/reference/redis_enterprise_database_api @@ -5,8 +5,9 @@ categories: - docs - operate @@ -39,10 +39,10 @@ index f925ce44..ea21766e 100644 --- apiVersion: -diff --git a/content/operate/kubernetes/reference/redis_enterprise_remote_cluster_api.md b/content/operate/kubernetes/reference/redis_enterprise_remote_cluster_api.md +diff --git a/content/operate/kubernetes/reference/redis_enterprise_remote_cluster_api b/content/operate/kubernetes/reference/redis_enterprise_remote_cluster_api index 7d37a6dc..a9a313cf 100644 ---- a/content/operate/kubernetes/reference/redis_enterprise_remote_cluster_api.md -+++ b/content/operate/kubernetes/reference/redis_enterprise_remote_cluster_api.md +--- a/content/operate/kubernetes/reference/redis_enterprise_remote_cluster_api ++++ b/content/operate/kubernetes/reference/redis_enterprise_remote_cluster_api @@ -5,7 +5,7 @@ categories: - docs - operate diff --git a/content/operate/kubernetes/reference/redis_enterprise_cluster_api.md b/content/operate/kubernetes/reference/redis_enterprise_cluster_api.md index 36a84f079..f2b8b0c5d 100644 --- a/content/operate/kubernetes/reference/redis_enterprise_cluster_api.md +++ b/content/operate/kubernetes/reference/redis_enterprise_cluster_api.md @@ -11701,7 +11701,7 @@ RS Cluster optional services settings -### spec.redisEnterpriseServicesConfiguration.mdnsServer +### spec.redisEnterpriseServicesConfigurationnsServer [↩ Parent](#specredisenterpriseservicesconfiguration) diff --git a/content/operate/kubernetes/release-notes/6-2-releases/k8s-6-2-10-34-2022-05.md b/content/operate/kubernetes/release-notes/6-2-releases/k8s-6-2-10-34-2022-05.md index 35bcfc9ca..9307dedbb 100644 --- a/content/operate/kubernetes/release-notes/6-2-releases/k8s-6-2-10-34-2022-05.md +++ b/content/operate/kubernetes/release-notes/6-2-releases/k8s-6-2-10-34-2022-05.md @@ -57,7 +57,7 @@ This release includes the following container images: ## Compatibility notes -Below is a table showing supported distributions at the time of this release. See [Supported Kubernetes distributions]({{< relref "/operate/kubernetes/reference/supported_k8s_distributions.md" >}}) for the current list of supported distributions. +Below is a table showing supported distributions at the time of this release. See [Supported Kubernetes distributions]({{< relref "/operate/kubernetes/reference/supported_k8s_distributions" >}}) for the current list of supported distributions. | **Kubernetes version** | **1.19** | **1.20** | **1.21** | **1.22** | **1.23** | |:------------------------|:----------:|:----------:|:----------:|:----------:|:----------:| diff --git a/content/operate/kubernetes/release-notes/6-2-releases/k8s-6-2-10-4-2022-03.md b/content/operate/kubernetes/release-notes/6-2-releases/k8s-6-2-10-4-2022-03.md index 690b3c940..4d316b6de 100644 --- a/content/operate/kubernetes/release-notes/6-2-releases/k8s-6-2-10-4-2022-03.md +++ b/content/operate/kubernetes/release-notes/6-2-releases/k8s-6-2-10-4-2022-03.md @@ -136,7 +136,7 @@ Contact support if your deployment is impacted. ## Compatibility Notes -See [Supported Kubernetes distributions]({{< relref "/operate/kubernetes/reference/supported_k8s_distributions.md" >}}) for the full list of supported distributions. +See [Supported Kubernetes distributions]({{< relref "/operate/kubernetes/reference/supported_k8s_distributions" >}}) for the full list of supported distributions. ### Now supported diff --git a/content/operate/kubernetes/release-notes/6-2-releases/k8s-6-2-10-45-2022-07.md b/content/operate/kubernetes/release-notes/6-2-releases/k8s-6-2-10-45-2022-07.md index a84820cb9..7a5f06be5 100644 --- a/content/operate/kubernetes/release-notes/6-2-releases/k8s-6-2-10-45-2022-07.md +++ b/content/operate/kubernetes/release-notes/6-2-releases/k8s-6-2-10-45-2022-07.md @@ -44,7 +44,7 @@ The `digestHash` optional field added to `imageSpec` fields in the REC. This fie ## Compatibility notes -Below is a table showing supported distributions at the time of this release. See [Supported Kubernetes distributions]({{< relref "/operate/kubernetes/reference/supported_k8s_distributions.md" >}}) for the current list of supported distributions. +Below is a table showing supported distributions at the time of this release. See [Supported Kubernetes distributions]({{< relref "/operate/kubernetes/reference/supported_k8s_distributions" >}}) for the current list of supported distributions. | **Kubernetes version** | 1.19 | 1.20 | 1.21 | 1.22 | 1.23 | 1.24 | |:------------------------|:----------:|:----------:|:----------:|:----------:|:----------:|:----------:| diff --git a/content/operate/kubernetes/release-notes/6-2-releases/k8s-6-2-12-1.md b/content/operate/kubernetes/release-notes/6-2-releases/k8s-6-2-12-1.md index c04d49463..fea340fe8 100644 --- a/content/operate/kubernetes/release-notes/6-2-releases/k8s-6-2-12-1.md +++ b/content/operate/kubernetes/release-notes/6-2-releases/k8s-6-2-12-1.md @@ -46,7 +46,7 @@ The Redis Enterprise cluster `podSecurityPolicy` is deprecated. This is still su ## Compatibility notes -Below is a table showing supported distributions at the time of this release. See [Supported Kubernetes distributions]({{< relref "/operate/kubernetes/reference/supported_k8s_distributions.md" >}}) for the current list of supported distributions. +Below is a table showing supported distributions at the time of this release. See [Supported Kubernetes distributions]({{< relref "/operate/kubernetes/reference/supported_k8s_distributions" >}}) for the current list of supported distributions. | **Kubernetes version** | 1.20 | 1.21 | 1.22 | 1.23 | 1.24 | |:------------------------|:----------:|:----------:|:----------:|:----------:|:----------:| diff --git a/content/operate/kubernetes/release-notes/6-2-releases/k8s-6-2-18-3.md b/content/operate/kubernetes/release-notes/6-2-releases/k8s-6-2-18-3.md index 7d9dc3b19..475ab33b7 100644 --- a/content/operate/kubernetes/release-notes/6-2-releases/k8s-6-2-18-3.md +++ b/content/operate/kubernetes/release-notes/6-2-releases/k8s-6-2-18-3.md @@ -32,7 +32,7 @@ This release includes the following container images: ## New features -* Support for [Auto Tiering]({{< relref "/operate/kubernetes/re-clusters/auto-tiering.md" >}}) (RED-78613) +* Support for [Auto Tiering]({{< relref "/operate/kubernetes/re-clusters/auto-tiering" >}}) (RED-78613) ## Feature improvements @@ -65,11 +65,11 @@ The following fields were added to the [Redis Enterprise cluster (REC) API]({{}}): -* `.isRoF` and `.rofRamSize` added to support the [Auto Tiering feature]({{< relref "/operate/kubernetes/re-clusters/auto-tiering.md" >}}). +* `.isRoF` and `.rofRamSize` added to support the [Auto Tiering feature]({{< relref "/operate/kubernetes/re-clusters/auto-tiering" >}}). ## Compatibility notes -Below is a table showing supported distributions at the time of this release. See [Supported Kubernetes distributions]({{< relref "/operate/kubernetes/reference/supported_k8s_distributions.md" >}}) for the current list of supported distributions. +Below is a table showing supported distributions at the time of this release. See [Supported Kubernetes distributions]({{< relref "/operate/kubernetes/reference/supported_k8s_distributions" >}}) for the current list of supported distributions. | **Kubernetes version** | 1.21 | 1.22 | 1.23 | 1.24 | 1.25 | |:------------------------|:----------:|:----------:|:----------:|:----------:|:----------:| diff --git a/content/operate/kubernetes/release-notes/6-2-releases/k8s-6-2-18-41-jan-2023.md b/content/operate/kubernetes/release-notes/6-2-releases/k8s-6-2-18-41-jan-2023.md index f85cfb29f..3f22bdecc 100644 --- a/content/operate/kubernetes/release-notes/6-2-releases/k8s-6-2-18-41-jan-2023.md +++ b/content/operate/kubernetes/release-notes/6-2-releases/k8s-6-2-18-41-jan-2023.md @@ -16,7 +16,7 @@ aliases: [ This is a maintenance release of Redis Enterprise for Kubernetes 6.2.18-41 that adds supports for Redis Enterprise 6.2.18-72. -New images and fixes are listed below. Refer to [6.2.18-41 (Dec 2022]({{< relref "/operate/kubernetes/release-notes/6-2-releases/k8s-6-2-18-41.md" >}}) for compatibility notes and known limitations. +New images and fixes are listed below. Refer to [6.2.18-41 (Dec 2022]({{< relref "/operate/kubernetes/release-notes/6-2-releases/k8s-6-2-18-41" >}}) for compatibility notes and known limitations. {{}} Due to a change in the SCC, on OpenShift clusters running version 6.2.12 or earlier upgrading to version 6.2.18 or later, where `node:1` is not the master node, the upgrade might get stuck. @@ -47,7 +47,7 @@ DockerHub images are available at `docker.io/`. ## Compatibility notes -See [Redis Enterprise for Kubernetes release notes 6.2.18-41 (Dec 2022)]({{< relref "/operate/kubernetes/release-notes/6-2-releases/k8s-6-2-18-41.md" >}}). +See [Redis Enterprise for Kubernetes release notes 6.2.18-41 (Dec 2022)]({{< relref "/operate/kubernetes/release-notes/6-2-releases/k8s-6-2-18-41" >}}). ## Before upgrading @@ -59,7 +59,7 @@ Be aware the following changes included in this release affect the upgrade proce ## Known limitations -See [Redis Enterprise for Kubernetes release notes 6.2.18-41 (Dec 2022)]({{< relref "/operate/kubernetes/release-notes/6-2-releases/k8s-6-2-18-41.md" >}}). +See [Redis Enterprise for Kubernetes release notes 6.2.18-41 (Dec 2022)]({{< relref "/operate/kubernetes/release-notes/6-2-releases/k8s-6-2-18-41" >}}). ## Security diff --git a/content/operate/kubernetes/release-notes/6-2-releases/k8s-6-2-18-41.md b/content/operate/kubernetes/release-notes/6-2-releases/k8s-6-2-18-41.md index 1a6bd7830..538e3e549 100644 --- a/content/operate/kubernetes/release-notes/6-2-releases/k8s-6-2-18-41.md +++ b/content/operate/kubernetes/release-notes/6-2-releases/k8s-6-2-18-41.md @@ -51,7 +51,7 @@ For more info and steps to prevent this issue, see [upgrade a Redis Enterprise c ## Compatibility notes -Below is a table showing supported distributions at the time of this release. See [Supported Kubernetes distributions]({{< relref "/operate/kubernetes/reference/supported_k8s_distributions.md" >}}) for the current list of supported distributions. +Below is a table showing supported distributions at the time of this release. See [Supported Kubernetes distributions]({{< relref "/operate/kubernetes/reference/supported_k8s_distributions" >}}) for the current list of supported distributions. | **Kubernetes version** | 1.21 | 1.22 | 1.23 | 1.24 | 1.25 | |:------------------------|:----------:|:----------:|:----------:|:----------:|:----------:| @@ -136,7 +136,7 @@ On clusters with more than 9 REC nodes, a Kubernetes upgrade can render the Redi * Following old revision of quick start guide causes issues creating an REDB due to unrecognized memory field name (RED-69515) - The workaround is to use the newer (current) revision of the [quick start document]({{< relref "/operate/kubernetes/deployment/quick-start.md" >}}) available online. + The workaround is to use the newer (current) revision of the [quick start document]({{< relref "/operate/kubernetes/deployment/quick-start" >}}) available online. * `autoUpgrade` set to true by operator might cause unexpected bdb upgrades when `redisUpgradePolicy` is set to true (RED-72351) diff --git a/content/operate/kubernetes/release-notes/6-2-releases/k8s-6-2-4-1-2021-09.md b/content/operate/kubernetes/release-notes/6-2-releases/k8s-6-2-4-1-2021-09.md index 90ef1ff3a..3be63494a 100644 --- a/content/operate/kubernetes/release-notes/6-2-releases/k8s-6-2-4-1-2021-09.md +++ b/content/operate/kubernetes/release-notes/6-2-releases/k8s-6-2-4-1-2021-09.md @@ -15,7 +15,7 @@ aliases: [ --- ## Overview -The Redis Enterprise [K8s 6.2.4-1](https://github.com/RedisLabs/redis-enterprise-k8s-docs/releases/tag/v6.2.4-1) release provides support for the [Redis Enterprise Software release 6.2.4]({{< relref "/operate/rs/release-notes/rs-6-2-4-august-2021.md" >}}) and includes several enhancements and bug fixes. +The Redis Enterprise [K8s 6.2.4-1](https://github.com/RedisLabs/redis-enterprise-k8s-docs/releases/tag/v6.2.4-1) release provides support for the [Redis Enterprise Software release 6.2.4]({{< relref "/operate/rs/release-notes/rs-6-2-4-august-2021" >}}) and includes several enhancements and bug fixes. The key new features, bug fixes, and known limitations are described below. @@ -145,7 +145,7 @@ The combined length of the REC name and namespace name must be equal to or less ## Compatibility Notes -See [Supported Kubernetes distributions]({{< relref "/operate/kubernetes/reference/supported_k8s_distributions.md" >}}) for the full list of supported distributions. +See [Supported Kubernetes distributions]({{< relref "/operate/kubernetes/reference/supported_k8s_distributions" >}}) for the full list of supported distributions. ### Now supported diff --git a/content/operate/kubernetes/release-notes/6-2-releases/k8s-6-2-8-11-2022-01.md b/content/operate/kubernetes/release-notes/6-2-releases/k8s-6-2-8-11-2022-01.md index de8de554b..79839f1e9 100644 --- a/content/operate/kubernetes/release-notes/6-2-releases/k8s-6-2-8-11-2022-01.md +++ b/content/operate/kubernetes/release-notes/6-2-releases/k8s-6-2-8-11-2022-01.md @@ -15,7 +15,7 @@ aliases: [ --- ## Overview -The Redis Enterprise K8s 6.2.8-11 release provides support for the [Redis Enterprise Software release 6.2.8]({{< relref "/operate/rs/release-notes/rs-6-2-8-october-2021.md" >}}) and includes several enhancements and bug fixes. +The Redis Enterprise K8s 6.2.8-11 release provides support for the [Redis Enterprise Software release 6.2.8]({{< relref "/operate/rs/release-notes/rs-6-2-8-october-2021" >}}) and includes several enhancements and bug fixes. The key new features, bug fixes, and known limitations are described below. @@ -136,7 +136,7 @@ The workaround is to use the newer (current) revision of the quick start documen ## Compatibility Notes -See [Supported Kubernetes distributions]({{< relref "/operate/kubernetes/reference/supported_k8s_distributions.md" >}}) for the full list of supported distributions. +See [Supported Kubernetes distributions]({{< relref "/operate/kubernetes/reference/supported_k8s_distributions" >}}) for the full list of supported distributions. ### Now supported diff --git a/content/operate/kubernetes/release-notes/6-2-releases/k8s-6-2-8-15-2022-01.md b/content/operate/kubernetes/release-notes/6-2-releases/k8s-6-2-8-15-2022-01.md index cda929958..e6b73e57e 100644 --- a/content/operate/kubernetes/release-notes/6-2-releases/k8s-6-2-8-15-2022-01.md +++ b/content/operate/kubernetes/release-notes/6-2-releases/k8s-6-2-8-15-2022-01.md @@ -9,12 +9,12 @@ description: Maintenance release with bug fixes linktitle: 6.2.8-15 (January 2022) weight: 64 aliases: [ - /operate/kubernetes/release-notes/k8s-6-2-8-15-2022-01.md, + /operate/kubernetes/release-notes/k8s-6-2-8-15-2022-01, ] --- ## Overview -The Redis Enterprise K8s 6.2.8-15 is a maintenance release for the [Redis Enterprise Software release 6.2.8]({{< relref "/operate/rs/release-notes/rs-6-2-8-october-2021.md" >}}) and includes bug fixes. +The Redis Enterprise K8s 6.2.8-15 is a maintenance release for the [Redis Enterprise Software release 6.2.8]({{< relref "/operate/rs/release-notes/rs-6-2-8-october-2021" >}}) and includes bug fixes. The key new features, bug fixes, and known limitations are described below. @@ -117,4 +117,4 @@ The workaround is to use the newer (current) revision of the quick start documen ## Compatibility Notes -See [Supported Kubernetes distributions]({{< relref "/operate/kubernetes/reference/supported_k8s_distributions.md" >}}) for the full list of supported distributions. +See [Supported Kubernetes distributions]({{< relref "/operate/kubernetes/reference/supported_k8s_distributions" >}}) for the full list of supported distributions. diff --git a/content/operate/kubernetes/release-notes/6-2-releases/k8s-6-2-8-2-2021-11.md b/content/operate/kubernetes/release-notes/6-2-releases/k8s-6-2-8-2-2021-11.md index f416f0cf9..6701c5cbe 100644 --- a/content/operate/kubernetes/release-notes/6-2-releases/k8s-6-2-8-2-2021-11.md +++ b/content/operate/kubernetes/release-notes/6-2-releases/k8s-6-2-8-2-2021-11.md @@ -14,7 +14,7 @@ aliases: [ --- ## Overview -The Redis Enterprise [K8s 6.2.8-2](https://github.com/RedisLabs/redis-enterprise-k8s-docs/releases/tag/v6.2.8-2) release provides support for the [Redis Enterprise Software release 6.2.8]({{< relref "/operate/rs/release-notes/rs-6-2-8-october-2021.md" >}}) and includes several enhancements and bug fixes. +The Redis Enterprise [K8s 6.2.8-2](https://github.com/RedisLabs/redis-enterprise-k8s-docs/releases/tag/v6.2.8-2) release provides support for the [Redis Enterprise Software release 6.2.8]({{< relref "/operate/rs/release-notes/rs-6-2-8-october-2021" >}}) and includes several enhancements and bug fixes. The key new features, bug fixes, and known limitations are described below. @@ -119,7 +119,7 @@ The workaround for this issue is to make sure you use integer values for the PVC ## Compatibility Notes -See [Supported Kubernetes distributions]({{< relref "/operate/kubernetes/reference/supported_k8s_distributions.md" >}}) for the full list of supported distributions. +See [Supported Kubernetes distributions]({{< relref "/operate/kubernetes/reference/supported_k8s_distributions" >}}) for the full list of supported distributions. ### No longer supported diff --git a/content/operate/kubernetes/release-notes/6-4-2-releases/6-4-2-5.md b/content/operate/kubernetes/release-notes/6-4-2-releases/6-4-2-5.md index 63f68f420..979733e03 100644 --- a/content/operate/kubernetes/release-notes/6-4-2-releases/6-4-2-5.md +++ b/content/operate/kubernetes/release-notes/6-4-2-releases/6-4-2-5.md @@ -13,7 +13,7 @@ weight: 56 This is a maintenance release of Redis Enterprise for Kubernetes 6.4.2-4 that adds supports for Redis Enterprise 6.4.2-61. -New images and fixes are listed below. Refer to [6.2.4-4 (March 2023)]({{< relref "/operate/kubernetes/release-notes/6-4-2-releases/k8s-6-4-2-4.md" >}}) for compatibility notes and known limitations. +New images and fixes are listed below. Refer to [6.2.4-4 (March 2023)]({{< relref "/operate/kubernetes/release-notes/6-4-2-releases/k8s-6-4-2-4" >}}) for compatibility notes and known limitations. ## Images @@ -42,7 +42,7 @@ New images and fixes are listed below. Refer to [6.2.4-4 (March 2023)]({{< relre ## Compatibility notes -See [Redis Enterprise for Kubernetes release notes 6.4.2-4 (March 2023)]({{< relref "/operate/kubernetes/release-notes/6-4-2-releases/k8s-6-4-2-4.md" >}}). +See [Redis Enterprise for Kubernetes release notes 6.4.2-4 (March 2023)]({{< relref "/operate/kubernetes/release-notes/6-4-2-releases/k8s-6-4-2-4" >}}). ## Before upgrading @@ -58,7 +58,7 @@ Be aware the following changes included in this release affect the upgrade proce ## Known limitations -See [Redis Enterprise for Kubernetes release notes 6.4.2-4 (March 2023)]({{< relref "/operate/kubernetes/release-notes/6-4-2-releases/k8s-6-4-2-4.md" >}}). +See [Redis Enterprise for Kubernetes release notes 6.4.2-4 (March 2023)]({{< relref "/operate/kubernetes/release-notes/6-4-2-releases/k8s-6-4-2-4" >}}). ## Security diff --git a/content/operate/kubernetes/release-notes/6-4-2-releases/6-4-2-6.md b/content/operate/kubernetes/release-notes/6-4-2-releases/6-4-2-6.md index c8eb1b07a..9dc3a3163 100644 --- a/content/operate/kubernetes/release-notes/6-4-2-releases/6-4-2-6.md +++ b/content/operate/kubernetes/release-notes/6-4-2-releases/6-4-2-6.md @@ -91,7 +91,7 @@ The following fields were changed in the [RedisEnterpriseCluster (REC) API]({{}}). +The following table shows supported distributions at the time of this release. You can also find this list in [Supported Kubernetes distributions]({{< relref "/operate/kubernetes/reference/supported_k8s_distributions" >}}). | **Kubernetes version** | 1.22 | 1.23 | 1.24 | 1.25 | 1.26 | 1.27 | @@ -150,7 +150,7 @@ Be aware the following changes included in this release affect the upgrade proce * **`autoUpgrade` set to `true` can cause unexpected bdb upgrades when `redisUpgradePolicy` is set to `true` (RED-72351)** Contact support if your deployment is impacted. -* **Following the previous quick start guide version causes issues with creating an REDB due to unrecognized memory field name (RED-69515)** The workaround is to use the newer (current) revision of the [quick start]({{< relref "/operate/kubernetes/deployment/quick-start.md" >}}). +* **Following the previous quick start guide version causes issues with creating an REDB due to unrecognized memory field name (RED-69515)** The workaround is to use the newer (current) revision of the [quick start]({{< relref "/operate/kubernetes/deployment/quick-start" >}}). * **PVC size issues when using decimal value in spec (RED-62132)** Make sure you use integer values for the PVC size. diff --git a/content/operate/kubernetes/release-notes/6-4-2-releases/k8s-6-4-2-4.md b/content/operate/kubernetes/release-notes/6-4-2-releases/k8s-6-4-2-4.md index acc4e6ded..ffb525c0e 100644 --- a/content/operate/kubernetes/release-notes/6-4-2-releases/k8s-6-4-2-4.md +++ b/content/operate/kubernetes/release-notes/6-4-2-releases/k8s-6-4-2-4.md @@ -74,7 +74,7 @@ The following fields were changed in the [Redis Enterprise cluster (REC) API]({{ ### Supported distributions -The following table shows supported distributions at the time of this release. You can also find this list in [Supported Kubernetes distributions]({{< relref "/operate/kubernetes/reference/supported_k8s_distributions.md" >}}). +The following table shows supported distributions at the time of this release. You can also find this list in [Supported Kubernetes distributions]({{< relref "/operate/kubernetes/reference/supported_k8s_distributions" >}}). | **Kubernetes version** | 1.21 | 1.22 | 1.23 | 1.24 | 1.25 | 1.26 | |:------------------------|:----------:|:----------:|:----------:|:----------:|:----------:|:----------:| @@ -186,7 +186,7 @@ On clusters with more than 9 REC nodes, a Kubernetes upgrade can render the Redi The workaround for this issue is to make sure you use integer values for the PVC size. * Following the previous quick start guide version causes issues with creating an REDB due to unrecognized memory field name (RED-69515) - The workaround is to use the newer (current) revision of the [quick start]({{< relref "/operate/kubernetes/deployment/quick-start.md" >}}). + The workaround is to use the newer (current) revision of the [quick start]({{< relref "/operate/kubernetes/deployment/quick-start" >}}). * `autoUpgrade` set to `true` can cause unexpected bdb upgrades when `redisUpgradePolicy` is set to `true` (RED-72351) Contact support if your deployment is impacted. diff --git a/content/operate/kubernetes/release-notes/7-8-6-releases/7-8-6-1-april2025.md b/content/operate/kubernetes/release-notes/7-8-6-releases/7-8-6-1-april2025.md index 275bff795..99d61c734 100644 --- a/content/operate/kubernetes/release-notes/7-8-6-releases/7-8-6-1-april2025.md +++ b/content/operate/kubernetes/release-notes/7-8-6-releases/7-8-6-1-april2025.md @@ -26,4 +26,4 @@ For supported distributions, known limitations, and API changes, see [Redis Ente ## Known limitations -See [7.8.6 releases]({{}}) for information on known limitations. +See [7.8.6 releases]({{}}) for information on known limitations. diff --git a/content/operate/kubernetes/release-notes/7-8-6-releases/7-8-6-1-march2025.md b/content/operate/kubernetes/release-notes/7-8-6-releases/7-8-6-1-march2025.md index 634ca6685..50d39bf98 100644 --- a/content/operate/kubernetes/release-notes/7-8-6-releases/7-8-6-1-march2025.md +++ b/content/operate/kubernetes/release-notes/7-8-6-releases/7-8-6-1-march2025.md @@ -13,15 +13,15 @@ weight: 50 ## New in the release -Redis Enterprise for Kubernetes 7.8.6-1 is a feature release that includes enhancements, bug fixes, platform updates, and support for [Redis Software 7.8.6-13]({{}}). +Redis Enterprise for Kubernetes 7.8.6-1 is a feature release that includes enhancements, bug fixes, platform updates, and support for [Redis Software 7.8.6-13]({{}}). -This release also includes the ability to [install the operator using Helm]({{}}). +This release also includes the ability to [install the operator using Helm]({{}}). Support for Helm is currently in public preview and is not supported on production workloads. Only new installations of the Redis operator are supported at this time. ### Enhancements -- Added support for [Redis Software 7.8.6-13]({{}}). +- Added support for [Redis Software 7.8.6-13]({{}}). - Updated supported Kubernetes distributions - DatabaseServicePortPolicy allows use of the default Redis port (6379) for database services. - Added additional license fields to the REC status. @@ -93,4 +93,4 @@ Any distribution not listed below is not supported for production workloads. ## Known limitations -See [7.8.6 releases]({{}}) for information on known limitations. +See [7.8.6 releases]({{}}) for information on known limitations. diff --git a/content/operate/kubernetes/release-notes/7-8-6-releases/7-8-6-1-may2025.md b/content/operate/kubernetes/release-notes/7-8-6-releases/7-8-6-1-may2025.md index 196cc5fb4..56dbbba1c 100644 --- a/content/operate/kubernetes/release-notes/7-8-6-releases/7-8-6-1-may2025.md +++ b/content/operate/kubernetes/release-notes/7-8-6-releases/7-8-6-1-may2025.md @@ -24,4 +24,4 @@ For supported distributions, known limitations, and API changes, see [Redis Ente ## Known limitations -See [7.8.6 releases]({{}}) for information on known limitations. +See [7.8.6 releases]({{}}) for information on known limitations. diff --git a/content/operate/kubernetes/release-notes/previous-releases/k8s-5-4-10-8.md b/content/operate/kubernetes/release-notes/previous-releases/k8s-5-4-10-8.md index 69d14c040..2d19624a3 100644 --- a/content/operate/kubernetes/release-notes/previous-releases/k8s-5-4-10-8.md +++ b/content/operate/kubernetes/release-notes/previous-releases/k8s-5-4-10-8.md @@ -10,13 +10,13 @@ linkTitle: 5.4.10-8 (January 2020) weight: 85 --- [Redis Enterprise for Kubernetes 5.4.10-8](https://github.com/RedisLabs/redis-enterprise-k8s-docs/releases/tag/5.4.10-8) is now available. -This release includes Redis Enterprise (RS) version [5.4.10-22]({{< relref "/operate/rs/release-notes/legacy-release-notes/rs-5-4-10-december-2019.md" >}}) and introduces new feature and bug fixes. +This release includes Redis Enterprise (RS) version [5.4.10-22]({{< relref "/operate/rs/release-notes/legacy-release-notes/rs-5-4-10-december-2019" >}}) and introduces new feature and bug fixes. ## Overview This is a maintenance release providing support for the Redis Enterprise Software release 5.4.10 and includes multiple enhancements. -Follow these [instructions]({{< relref "/operate/kubernetes/upgrade/upgrade-redis-cluster.md" >}}) for upgrading to this Kubernetes operator release. +Follow these [instructions]({{< relref "/operate/kubernetes/upgrade/upgrade-redis-cluster" >}}) for upgrading to this Kubernetes operator release. ## New features @@ -26,12 +26,12 @@ Follow these [instructions]({{< relref "/operate/kubernetes/upgrade/upgrade-redi Pay special attention to the yaml file naming changes and new yaml files that have been created for this release. These are highlighted in the quick start guide. {{< /note >}} -- Rack Awareness - Support for the [Redis Software Rack Awareness][{{< relref "/operate/rs/clusters/configure/rack-zone-awareness.md" >}}] feature was introduced to the Kubernetes deployment. It enables deploying nodes to different zones, in a multi-zone Kubernetes cluster. Databases that are rack-aware will have the cluster populate their master shard and replica shards in different nodes, across different zones or failure domains. This enables maintaining data persistence in case of zone failure. +- Rack Awareness - Support for the [Redis Software Rack Awareness][{{< relref "/operate/rs/clusters/configure/rack-zone-awareness" >}}] feature was introduced to the Kubernetes deployment. It enables deploying nodes to different zones, in a multi-zone Kubernetes cluster. Databases that are rack-aware will have the cluster populate their master shard and replica shards in different nodes, across different zones or failure domains. This enables maintaining data persistence in case of zone failure. - OLM Support - Redis Enterprise for Kubernetes is now RedHat OpenShift certified and can be effortlessly configured and deployed in Kubernetes clusters supporting OLM, including OpenShift 4.x clusters, with just a few clicks. OLM based deployments do not require Kubernetes cluster administrator rights to deploy the operator. - Improve cluster nodes' pod scheduling resiliency - Redis Enterprise Cluster pod scheduling is hardened by implementing Kubernetes best practices and providing configuration recommendations to cluster operators. Scheduling resiliency minimizes the chance of cluster node pods eviction or failure to schedule. -See the top 4 articles in the new [Additonal Topics](https://github.com/RedisLabs/redis-enterprise-k8s-docs/blob/92a2eff4b8c4ccafac459138f12e5f38acde825c/docs/topics.md#additional-topics) documentation section. +See the top 4 articles in the new [Additonal Topics](https://github.com/RedisLabs/redis-enterprise-k8s-docs/blob/92a2eff4b8c4ccafac459138f12e5f38acde825c/docs/topics#additional-topics) documentation section. - Update app.redislabs.com API version to stable - We've updated the Redis Enterprise Cluster custom resource API from [alpha to stable](https://kubernetes.io/docs/concepts/overview/kubernetes-api/#api-versioning) to reflect the current state of maturity of our implementation. @@ -48,4 +48,4 @@ For legacy Kubernetes versions, deployment files are available in the documentat - Custom Resource Definition Changes - In order to comply with OLM best practices, a change was required to the Redis Enterprise Cluster Custom Resource Defintion (CRD) to introduce the status sub-resource. As a result of this change, any upgrade from an older release to this release requires a change to the CRD. Once the CRD is updated, all Redis Enterprise Clusters in the same K8s cluster must be updated to the latest release in order to continue operating properly. -- Cluster Recovery - {{< embed-md "force-delete-pods.md" >}} +- Cluster Recovery - {{< embed-md "force-delete-pods" >}} diff --git a/content/operate/kubernetes/release-notes/previous-releases/k8s-6-0-12-5.md b/content/operate/kubernetes/release-notes/previous-releases/k8s-6-0-12-5.md index 3a7a3cb30..021997668 100644 --- a/content/operate/kubernetes/release-notes/previous-releases/k8s-6-0-12-5.md +++ b/content/operate/kubernetes/release-notes/previous-releases/k8s-6-0-12-5.md @@ -21,7 +21,7 @@ This release of the operator provides: * Various bug fixes -To upgrade your deployment to this latest release, see ["Upgrade a Redis Enterprise cluster (REC) on Kubernetes"]({{< relref "/operate/kubernetes/upgrade/upgrade-redis-cluster.md" >}}). +To upgrade your deployment to this latest release, see ["Upgrade a Redis Enterprise cluster (REC) on Kubernetes"]({{< relref "/operate/kubernetes/upgrade/upgrade-redis-cluster" >}}). ## Images diff --git a/content/operate/kubernetes/release-notes/previous-releases/k8s-6-0-20-4.md b/content/operate/kubernetes/release-notes/previous-releases/k8s-6-0-20-4.md index 1a6cfd532..74c0ee063 100644 --- a/content/operate/kubernetes/release-notes/previous-releases/k8s-6-0-20-4.md +++ b/content/operate/kubernetes/release-notes/previous-releases/k8s-6-0-20-4.md @@ -11,7 +11,7 @@ linktitle: 6.0.20-4 (May 2021) weight: 69 --- -The Redis Enterprise K8s [6.0.20-4](https://github.com/RedisLabs/redis-enterprise-k8s-docs/releases/tag/v6.0.20-4) release is a *major release* on top of [6.0.8-20](https://github.com/RedisLabs/redis-enterprise-k8s-docs/releases/tag/v6.0.8-20) providing support for the [Redis Enterprise Software release 6.0.20-69]({{< relref "/operate/rs/release-notes/rs-6-0-20-april-2021.md" >}}) and includes several enhancements and bug fixes. +The Redis Enterprise K8s [6.0.20-4](https://github.com/RedisLabs/redis-enterprise-k8s-docs/releases/tag/v6.0.20-4) release is a *major release* on top of [6.0.8-20](https://github.com/RedisLabs/redis-enterprise-k8s-docs/releases/tag/v6.0.8-20) providing support for the [Redis Enterprise Software release 6.0.20-69]({{< relref "/operate/rs/release-notes/rs-6-0-20-april-2021" >}}) and includes several enhancements and bug fixes. ## Overview @@ -19,7 +19,7 @@ This release of the operator provides: * New features * Various bug fixes -To upgrade your deployment to this latest release, see ["Upgrade a Redis Enterprise cluster (REC) on Kubernetes"]({{< relref "/operate/kubernetes/upgrade/upgrade-redis-cluster.md" >}}). +To upgrade your deployment to this latest release, see ["Upgrade a Redis Enterprise cluster (REC) on Kubernetes"]({{< relref "/operate/kubernetes/upgrade/upgrade-redis-cluster" >}}). ## Images This release includes the following container images: diff --git a/content/operate/kubernetes/release-notes/previous-releases/k8s-6-0-6-11.md b/content/operate/kubernetes/release-notes/previous-releases/k8s-6-0-6-11.md index d964dcf39..bb7e75176 100644 --- a/content/operate/kubernetes/release-notes/previous-releases/k8s-6-0-6-11.md +++ b/content/operate/kubernetes/release-notes/previous-releases/k8s-6-0-6-11.md @@ -19,7 +19,7 @@ This release of the operator provides: - Support for the Redis Enterprise Software release 6.0.6-39 - Various bug fixes -To upgrade your deployment to this latest release, see ["Upgrade a Redis Enterprise cluster (REC) on Kubernetes"]({{< relref "/operate/kubernetes/upgrade/upgrade-redis-cluster.md" >}}). +To upgrade your deployment to this latest release, see ["Upgrade a Redis Enterprise cluster (REC) on Kubernetes"]({{< relref "/operate/kubernetes/upgrade/upgrade-redis-cluster" >}}). ## Images diff --git a/content/operate/kubernetes/release-notes/previous-releases/k8s-6-0-6-23.md b/content/operate/kubernetes/release-notes/previous-releases/k8s-6-0-6-23.md index c06a7c6f0..7fd999643 100644 --- a/content/operate/kubernetes/release-notes/previous-releases/k8s-6-0-6-23.md +++ b/content/operate/kubernetes/release-notes/previous-releases/k8s-6-0-6-23.md @@ -23,7 +23,7 @@ This release of the operator provides: - UBI images - Various other enhancements and bug fixes -To upgrade your deployment to this latest release, see ["Upgrade a Redis Enterprise cluster (REC) on Kubernetes"]({{< relref "/operate/kubernetes/upgrade/upgrade-redis-cluster.md" >}}). +To upgrade your deployment to this latest release, see ["Upgrade a Redis Enterprise cluster (REC) on Kubernetes"]({{< relref "/operate/kubernetes/upgrade/upgrade-redis-cluster" >}}). ## Images @@ -37,13 +37,13 @@ To upgrade your deployment to this latest release, see ["Upgrade a Redis Enterpr - Rancher support (RED37918) - The operator is now supported on [Rancher](https://rancher.com/) version ([v2.4.5](https://rancher.com/support-maintenance-terms/all-supported-versions/rancher-v2.4.5/)). Note that since this release of the operator doesn't support K8s 1.18, it requires one of the other supported upstread version in this Rancher release, i.e. 1.15.12, 1.16.13 or 1.17.9. -- Database Replica Of support (RED40160) - Support for [Replica Of](https://docs.redislabs.com/latest/rs/administering/active-passive/) was added to the [DB controller](https://github.com/RedisLabs/redis-enterprise-k8s-docs/blob/master/redis_enterprise_database_api.md#replicasource). +- Database Replica Of support (RED40160) - Support for [Replica Of](https://docs.redislabs.com/latest/rs/administering/active-passive/) was added to the [DB controller](https://github.com/RedisLabs/redis-enterprise-k8s-docs/blob/master/redis_enterprise_database_api#replicasource). -- Database backup configuration (RED40165) - Support for [backup configuration](https://docs.redislabs.com/latest/rs/administering/database-operations/database-backup/) was added to the [DB controller spec](https://github.com/RedisLabs/redis-enterprise-k8s-docs/blob/master/redis_enterprise_database_api.md#backupspec). +- Database backup configuration (RED40165) - Support for [backup configuration](https://docs.redislabs.com/latest/rs/administering/database-operations/database-backup/) was added to the [DB controller spec](https://github.com/RedisLabs/redis-enterprise-k8s-docs/blob/master/redis_enterprise_database_api#backupspec). -- Alert configuration (RED40166) - Support for alert configuration was added to the [DB controller spec](https://github.com/RedisLabs/redis-enterprise-k8s-docs/blob/master/redis_enterprise_database_api.md#dbalertssettings). +- Alert configuration (RED40166) - Support for alert configuration was added to the [DB controller spec](https://github.com/RedisLabs/redis-enterprise-k8s-docs/blob/master/redis_enterprise_database_api#dbalertssettings). -- Database TLS configuration (RED41758) - Support for TLS authentication configuration was added to the [DB controller spec](https://github.com/RedisLabs/redis-enterprise-k8s-docs/blob/0ec741ffb3d621d371b5eec5b0a045ee7364e50e/redis_enterprise_database_api.md#redisenterprisedatabasespec). +- Database TLS configuration (RED41758) - Support for TLS authentication configuration was added to the [DB controller spec](https://github.com/RedisLabs/redis-enterprise-k8s-docs/blob/0ec741ffb3d621d371b5eec5b0a045ee7364e50e/redis_enterprise_database_api#redisenterprisedatabasespec). - OpenShift 4.4 support (RED41352) - The operator is now supported on [Openshift 4.4](https://docs.openshift.com/container-platform/4.4/welcome/index.html). diff --git a/content/operate/kubernetes/release-notes/previous-releases/k8s-6-0-6-24.md b/content/operate/kubernetes/release-notes/previous-releases/k8s-6-0-6-24.md index 1483c9022..ba3ea7dca 100644 --- a/content/operate/kubernetes/release-notes/previous-releases/k8s-6-0-6-24.md +++ b/content/operate/kubernetes/release-notes/previous-releases/k8s-6-0-6-24.md @@ -19,7 +19,7 @@ This release of the operator provides: * Various bug fixes -To upgrade your deployment to this latest release, see ["Upgrade a Redis Enterprise cluster (REC) on Kubernetes"]({{< relref "/operate/kubernetes/upgrade/upgrade-redis-cluster.md" >}}). +To upgrade your deployment to this latest release, see ["Upgrade a Redis Enterprise cluster (REC) on Kubernetes"]({{< relref "/operate/kubernetes/upgrade/upgrade-redis-cluster" >}}). ## Images diff --git a/content/operate/kubernetes/release-notes/previous-releases/k8s-6-0-6-6.md b/content/operate/kubernetes/release-notes/previous-releases/k8s-6-0-6-6.md index f967cf86b..b78be11f9 100644 --- a/content/operate/kubernetes/release-notes/previous-releases/k8s-6-0-6-6.md +++ b/content/operate/kubernetes/release-notes/previous-releases/k8s-6-0-6-6.md @@ -10,7 +10,7 @@ description: Support for RS 6.0.6, new database and admission controllers, vario linkTitle: 6.0.6-6 (June 2020) weight: 80 --- -Redis Enterprise for Kubernetes 6.0.6-6 is now available. This release includes Redis Enterprise (RS) version [6.0]({{< relref "/operate/rs/release-notes/rs-6-0-may-2020.md" >}}) and introduces new features, improvements, and bug fixes. +Redis Enterprise for Kubernetes 6.0.6-6 is now available. This release includes Redis Enterprise (RS) version [6.0]({{< relref "/operate/rs/release-notes/rs-6-0-may-2020" >}}) and introduces new features, improvements, and bug fixes. ## Overview @@ -20,7 +20,7 @@ This release of the operator provides: - Includes the new database and admission controllers - Various improvements and bug fixes -To upgrade your deployment to this latest release, see ["Upgrade a Redis Enterprise cluster (REC) on Kubernetes"]({{< relref "/operate/kubernetes/upgrade/upgrade-redis-cluster.md" >}}). +To upgrade your deployment to this latest release, see ["Upgrade a Redis Enterprise cluster (REC) on Kubernetes"]({{< relref "/operate/kubernetes/upgrade/upgrade-redis-cluster" >}}). {{< note >}} If you are running Active-Active (CRBD) databases on a previous release, do not upgrade to 6.0.6-6 at this time. There is an issue with the upgrade process that is currently being investigated (RED43635). For more information and support please [contact Redis support](https://redislabs.com/company/support/). diff --git a/content/operate/kubernetes/release-notes/previous-releases/k8s-6-0-8-1.md b/content/operate/kubernetes/release-notes/previous-releases/k8s-6-0-8-1.md index 96b025a98..cf9f293e9 100644 --- a/content/operate/kubernetes/release-notes/previous-releases/k8s-6-0-8-1.md +++ b/content/operate/kubernetes/release-notes/previous-releases/k8s-6-0-8-1.md @@ -22,7 +22,7 @@ This release of the operator provides: * Various bug fixes -To upgrade your deployment to this latest release, see ["Upgrade a Redis Enterprise cluster (REC) on Kubernetes"]({{< relref "/operate/kubernetes/upgrade/upgrade-redis-cluster.md" >}}). +To upgrade your deployment to this latest release, see ["Upgrade a Redis Enterprise cluster (REC) on Kubernetes"]({{< relref "/operate/kubernetes/upgrade/upgrade-redis-cluster" >}}). ## Images @@ -33,7 +33,7 @@ To upgrade your deployment to this latest release, see ["Upgrade a Redis Enterpr ## New features - * Redis [Modules](https://redislabs.com/redis-enterprise/modules/) can now be [configured](https://github.com/RedisLabs/redis-enterprise-k8s-docs/blob/master/redis_enterprise_database_api.md#dbmodule) in the database custom resource. + * Redis [Modules](https://redislabs.com/redis-enterprise/modules/) can now be [configured](https://github.com/RedisLabs/redis-enterprise-k8s-docs/blob/master/redis_enterprise_database_api#dbmodule) in the database custom resource. * Support was added for **[OpenShift 4.5](https://docs.openshift.com/container-platform/4.5/release_notes/ocp-4-5-release-notes.html)** * Support was added for **Kubernetes 1.18** * Added support for the Gesher admission control proxy to provide an administrator the ability to setup delegation to avoid the need for administrator intervention on every namespaced deployed operator. diff --git a/content/operate/kubernetes/release-notes/previous-releases/k8s-6-0-8-20.md b/content/operate/kubernetes/release-notes/previous-releases/k8s-6-0-8-20.md index 843d2e8f4..4125ddc9a 100644 --- a/content/operate/kubernetes/release-notes/previous-releases/k8s-6-0-8-20.md +++ b/content/operate/kubernetes/release-notes/previous-releases/k8s-6-0-8-20.md @@ -20,7 +20,7 @@ This release of the operator provides: * New features * Various bug fixes -To upgrade your deployment to this latest release, see ["Upgrade a Redis Enterprise cluster (REC) on Kubernetes"]({{< relref "/operate/kubernetes/upgrade/upgrade-redis-cluster.md" >}}). +To upgrade your deployment to this latest release, see ["Upgrade a Redis Enterprise cluster (REC) on Kubernetes"]({{< relref "/operate/kubernetes/upgrade/upgrade-redis-cluster" >}}). ## Images This release includes the following container images: diff --git a/content/operate/kubernetes/security/internode-encryption.md b/content/operate/kubernetes/security/internode-encryption.md index 445345e3b..08400ed8a 100644 --- a/content/operate/kubernetes/security/internode-encryption.md +++ b/content/operate/kubernetes/security/internode-encryption.md @@ -27,4 +27,4 @@ spec: dataInternodeEncryption: false ``` -To learn more about internode encryption, see [Internode encryption for Redis Enterprise Software]({{< relref "/operate/rs/security/encryption/internode-encryption.md" >}}). +To learn more about internode encryption, see [Internode encryption for Redis Enterprise Software]({{< relref "/operate/rs/security/encryption/internode-encryption" >}}). diff --git a/content/operate/kubernetes/security/ldap.md b/content/operate/kubernetes/security/ldap.md index e83961864..978acc128 100644 --- a/content/operate/kubernetes/security/ldap.md +++ b/content/operate/kubernetes/security/ldap.md @@ -16,7 +16,7 @@ Redis Enterprise Software supports LDAP authentication and authorization through Redis Enterprise for Kubernetes supports enabling and configuring LDAP authentication using the `RedisEnterpriseCluster` (REC) custom resource. Currently, the Redis Enterprise cluster (REC) only supports configuration related to the LDAP server, such as server addresses, connection details, credentials, and query configuration. -To [map LDAP groups to Redis Enterprise access control roles]({{< relref "/operate/rs/security/access-control/ldap/enable-role-based-ldap.md" >}}), you'll need to use the Redis Enterprise [API]({{< relref "/operate/rs/references/rest-api/requests/ldap_mappings/" >}}) or [admin console]({{< relref "/operate/rs/security/access-control/ldap/enable-role-based-ldap.md" >}}). +To [map LDAP groups to Redis Enterprise access control roles]({{< relref "/operate/rs/security/access-control/ldap/enable-role-based-ldap" >}}), you'll need to use the Redis Enterprise [API]({{< relref "/operate/rs/references/rest-api/requests/ldap_mappings/" >}}) or [admin console]({{< relref "/operate/rs/security/access-control/ldap/enable-role-based-ldap" >}}). ## Enable LDAP @@ -46,7 +46,7 @@ spec: attribute: memberOf ``` -Refer to the `RedisEnterpriseCluster` [API reference](https://github.com/RedisLabs/redis-enterprise-k8s-docs/blob/master/redis_enterprise_cluster_api.md#ldapspec) for full details on the available fields. +Refer to the `RedisEnterpriseCluster` [API reference](https://github.com/RedisLabs/redis-enterprise-k8s-docs/blob/master/redis_enterprise_cluster_api#ldapspec) for full details on the available fields. ### Bind credentials @@ -162,6 +162,6 @@ Redis Enterprise Software can't resolve DNS names with a `.local` suffix. ## Next steps -To [map LDAP groups to Redis Enterprise access control roles]({{< relref "/operate/rs/security/access-control/ldap/enable-role-based-ldap.md" >}}), you'll need to use the Redis Enterprise [API]({{< relref "/operate/rs/references/rest-api/requests/ldap_mappings/" >}}) or [admin console]({{< relref "/operate/rs/security/access-control/ldap/enable-role-based-ldap.md" >}}). +To [map LDAP groups to Redis Enterprise access control roles]({{< relref "/operate/rs/security/access-control/ldap/enable-role-based-ldap" >}}), you'll need to use the Redis Enterprise [API]({{< relref "/operate/rs/references/rest-api/requests/ldap_mappings/" >}}) or [admin console]({{< relref "/operate/rs/security/access-control/ldap/enable-role-based-ldap" >}}). For more details on how LDAP works with Redis Enterprise, see [LDAP authentication]({{< relref "/operate/rs/security/access-control/ldap/" >}}). diff --git a/content/operate/kubernetes/security/manage-rec-credentials.md b/content/operate/kubernetes/security/manage-rec-credentials.md index 5a553336a..1657e880a 100644 --- a/content/operate/kubernetes/security/manage-rec-credentials.md +++ b/content/operate/kubernetes/security/manage-rec-credentials.md @@ -99,7 +99,7 @@ curl -k --request DELETE \ ### Change both the REC username and password -1. [Connect to the admin console]({{< relref "/operate/kubernetes/re-clusters/connect-to-admin-console.md" >}}) +1. [Connect to the admin console]({{< relref "/operate/kubernetes/re-clusters/connect-to-admin-console" >}}) 2. [Add another admin user]({{< relref "/operate/rs/security/access-control/create-users" >}}) and choose a new password. @@ -133,4 +133,4 @@ If you store your secrets with Hashicorp Vault, update the secret for the REC cr username:, password: ``` -For more information about Vault integration with the Redis Enterprise Cluster see [Integrating Redis Enterprise for Kubernetes with Hashicorp Vault](https://github.com/RedisLabs/redis-enterprise-k8s-docs/blob/master/vault/README.md). +For more information about Vault integration with the Redis Enterprise Cluster see [Integrating Redis Enterprise for Kubernetes with Hashicorp Vault](https://github.com/RedisLabs/redis-enterprise-k8s-docs/blob/master/vault/README). diff --git a/content/operate/kubernetes/upgrade/_index.md b/content/operate/kubernetes/upgrade/_index.md index 60c6588e9..4af84dc9d 100644 --- a/content/operate/kubernetes/upgrade/_index.md +++ b/content/operate/kubernetes/upgrade/_index.md @@ -25,7 +25,7 @@ For all other Kubernetes distributions, see [Upgrade Redis Enterprise for Kubern When upgrading, both your Kubernetes version and Redis operator version need to be supported at all times. -{{}}If your current Kubernetes distribution is not [supported]({{}}), upgrade to a supported distribution before upgrading. {{}} +{{}}If your current Kubernetes distribution is not [supported]({{}}), upgrade to a supported distribution before upgrading. {{}} ## RHEL9-based image diff --git a/content/operate/kubernetes/upgrade/openshift-cli.md b/content/operate/kubernetes/upgrade/openshift-cli.md index cd2a2f651..82d92ad68 100644 --- a/content/operate/kubernetes/upgrade/openshift-cli.md +++ b/content/operate/kubernetes/upgrade/openshift-cli.md @@ -104,10 +104,10 @@ deployment.apps/redis-enterprise-operator configured If you have the admission controller enabled, you need to manually reapply the `ValidatingWebhookConfiguration`. {{}} -{{< embed-md "k8s-642-redb-admission-webhook-name-change.md" >}} +{{< embed-md "k8s-642-redb-admission-webhook-name-change" >}} {{}} -{{< embed-md "k8s-admission-webhook-cert.md" >}} +{{< embed-md "k8s-admission-webhook-cert" >}} ### Verify the operator is running diff --git a/content/operate/kubernetes/upgrade/upgrade-redis-cluster.md b/content/operate/kubernetes/upgrade/upgrade-redis-cluster.md index 43b6b6c54..25f1c2a07 100644 --- a/content/operate/kubernetes/upgrade/upgrade-redis-cluster.md +++ b/content/operate/kubernetes/upgrade/upgrade-redis-cluster.md @@ -105,10 +105,10 @@ deployment.apps/redis-enterprise-operator configured If you have the admission controller enabled, you need to manually reapply the `ValidatingWebhookConfiguration`. {{}} -{{< embed-md "k8s-642-redb-admission-webhook-name-change.md" >}} +{{< embed-md "k8s-642-redb-admission-webhook-name-change" >}} {{}} -{{< embed-md "k8s-admission-webhook-cert.md" >}} +{{< embed-md "k8s-admission-webhook-cert" >}} ### Verify the operator is running