diff --git a/content/operate/kubernetes/7.4.6/architecture/operator.md b/content/operate/kubernetes/7.4.6/architecture/operator.md index 8f9ddb3a21..264afffdc3 100644 --- a/content/operate/kubernetes/7.4.6/architecture/operator.md +++ b/content/operate/kubernetes/7.4.6/architecture/operator.md @@ -50,7 +50,7 @@ resources - Logging events - Enabling a simple mechanism for editing the Cluster spec -The Redis Enterprise operator functions as the logic “glue” between the +The Redis Enterprise operator functions as the logic "glue" between the K8s infrastructure and the Redis Enterprise Cluster. The operator creates the following resources: diff --git a/content/operate/kubernetes/7.4.6/deployment/openshift/old-index.md b/content/operate/kubernetes/7.4.6/deployment/openshift/old-index.md index ad4cf67e12..47430d50e3 100644 --- a/content/operate/kubernetes/7.4.6/deployment/openshift/old-index.md +++ b/content/operate/kubernetes/7.4.6/deployment/openshift/old-index.md @@ -38,7 +38,7 @@ Prerequisites: {{< image filename="/images/rs/getting-started-kubernetes-openshift-image1.png" >}} -- Click on “admin” (upper right corner) and then “Copy Login.” +- Click on "admin" (upper right corner) and then "Copy Login." {{< image filename="/images/rs/getting-started-kubernetes-openshift-image4.png" >}} @@ -89,7 +89,7 @@ Let’s look at each yaml file to see what requires editing: You should receive the following response: ```sh - securitycontextconstraints.security.openshift.io “redis-enterprise-scc” configured + securitycontextconstraints.security.openshift.io "redis-enterprise-scc" configured ``` Now you need to bind the scc to your project by typing: @@ -98,7 +98,7 @@ Let’s look at each yaml file to see what requires editing: oc adm policy add-scc-to-group redis-enterprise-scc system:serviceaccounts:your_project_name ``` - (If you do not remember your project name, run “oc project”) + (If you do not remember your project name, run "oc project") - [openshift.bundle.yaml](https://github.com/RedisLabs/redis-enterprise-k8s-docs/blob/master/openshift.bundle.yaml) - @@ -215,15 +215,15 @@ Now, run `kubectl get deployment` and verify that your redis-enterprise-operator This yaml can be edited to the required use case, however, the sample provided can be used for test/dev and quick start purposes. Here are the main fields you may review and edit: - - name: “your_cluster_name” (e.g. “demo-cluster”) + - name: "your_cluster_name" (e.g. "demo-cluster") - nodes: number_of_nodes_in_the_cluster (Must be an uneven number of at least 3 or greater—[here’s why](https://redislabs.com/redis-enterprise/technology/highly-available-redis/)) - uiServiceType: service_type Service type value can be either ClusterIP or LoadBalancer. This is an optional configuration based on [k8s service types](https://kubernetes.io/docs/tutorials/kubernetes-basics/expose/expose-intro/). The default is ClusterIP. - - storageClassName: “gp2“ + - storageClassName: "gp2" - This specifies the [StorageClass](https://kubernetes.io/docs/concepts/storage/storage-classes/) used for your nodes’ persistent disks. For example, AWS uses “gp2” as a default, GKE uses “standard” and Azure uses "default"). + This specifies the [StorageClass](https://kubernetes.io/docs/concepts/storage/storage-classes/) used for your nodes’ persistent disks. For example, AWS uses "gp2" as a default, GKE uses "standard" and Azure uses "default"). - redisEnterpriseNodeResources: The [compute resources](https://docs.openshift.com/enterprise/3.2/dev_guide/compute_resources.html#dev-compute-resources) required for each node. - limits – specifies the max resources for a Redis node @@ -233,11 +233,11 @@ Now, run `kubectl get deployment` and verify that your redis-enterprise-operator ```sh limits - cpu: “4000m” + cpu: "4000m" memory: 4Gi requests - cpu: “4000m” + cpu: "4000m" memory: 4Gi ``` @@ -250,10 +250,10 @@ Resource limits should equal requests ([Learn why](https://github.com/RedisLabs/ - serviceBrokerSpec – - enabled: \ - This specifies [persistence](https://redislabs.com/redis-features/persistence) for the Service Broker with an “enabled/disabled” flag. The default is “false.” + This specifies [persistence](https://redislabs.com/redis-features/persistence) for the Service Broker with an "enabled/disabled" flag. The default is "false." persistentSpec: - storageClassName: “gp2“ + storageClassName: "gp2" - redisEnterpriseImageSpec: This configuration controls the Redis Enterprise version used, and where it is fetched from. This is an optional field. The Operator will automatically use the matching RHEL image version for the release. @@ -272,7 +272,7 @@ Once you have your_cluster_name yaml set, you need to apply it to create your Re kubectl apply -f your_cluster_name.yaml ``` -Run kubectl get rec and verify that creation was successful (rec is a shortcut for “RedisEnterpriseClusters”). +Run kubectl get rec and verify that creation was successful (rec is a shortcut for "RedisEnterpriseClusters"). You should receive a response similar to the following: @@ -325,7 +325,7 @@ In order to create your database, we will log in to the Redis Enterprise UI. {{< image filename="/images/rs/getting-started-kubernetes-openshift-image5.png" >}} - In order to retrieve your password, navigate to the OpenShift management console, select your project name, go to Resources-\>Secrets-\>your_cluster_name -- Retrieve your password by selecting “Reveal Secret.” +- Retrieve your password by selecting "Reveal Secret." {{< warning >}} Do not change the default admin user password in the Redis Enterprise admin console. diff --git a/content/operate/kubernetes/7.4.6/faqs/_index.md b/content/operate/kubernetes/7.4.6/faqs/_index.md index 3cbe831eb2..bbf430dd5b 100644 --- a/content/operate/kubernetes/7.4.6/faqs/_index.md +++ b/content/operate/kubernetes/7.4.6/faqs/_index.md @@ -113,7 +113,7 @@ metadata: kind: RedisEnterpriseCluster name: test uid: 8b247469-c715-11e8-a5d5-0a778671fc2e - resourceVersion: “911969” + resourceVersion: "911969" selfLink: /api/v1/namespaces/redis/secrets/redis-enterprise-cluster uid: 8c4ff52e-c715-11e8-80f5-02cc4fca9682 type: Opaque @@ -130,7 +130,7 @@ echo "Q2h5N1BBY28=" | base64 –-decode To retrieve your password, navigate to the OpenShift management console, select your project name, go to Resources->Secrets->your_cluster_name -Retrieve your password by selecting “Reveal Secret.” +Retrieve your password by selecting "Reveal Secret." {{< image filename="/images/rs/openshift-password-retrieval.png" >}} diff --git a/content/operate/kubernetes/7.4.6/recommendations/persistent-volumes.md b/content/operate/kubernetes/7.4.6/recommendations/persistent-volumes.md index 431f18428d..a102bc4bc7 100644 --- a/content/operate/kubernetes/7.4.6/recommendations/persistent-volumes.md +++ b/content/operate/kubernetes/7.4.6/recommendations/persistent-volumes.md @@ -29,7 +29,7 @@ spec should include a *persistentSpec* section, in the persistentSpec: enabled: true storageClassName: "standard" - volumeSize: "23Gi” #optional + volumeSize: "23Gi" #optional Persistence storage is a requirement for production deployments. @@ -71,7 +71,7 @@ deployment, use the following command: kubectl get StorageClass -Typically, AWS provides “gp2” as the Storage Class name while GKE uses “standard.” +Typically, AWS provides "gp2" as the Storage Class name while GKE uses "standard." Azure provides two Storage Classes: "default" using HDDs, and "managed-premium" using SSDs. Below is an example of a response to the command. @@ -101,8 +101,8 @@ Example of the redisEnterpriseNodeResources definition: redisEnterpriseNodeResources: limits: - cpu: “4000m” + cpu: "4000m" memory: 4Gi requests: - cpu: “4000m” + cpu: "4000m" memory: 4Gi diff --git a/content/operate/kubernetes/7.4.6/recommendations/sizing-on-kubernetes.md b/content/operate/kubernetes/7.4.6/recommendations/sizing-on-kubernetes.md index ab3fb8b1d1..d0e5faa96b 100644 --- a/content/operate/kubernetes/7.4.6/recommendations/sizing-on-kubernetes.md +++ b/content/operate/kubernetes/7.4.6/recommendations/sizing-on-kubernetes.md @@ -70,13 +70,13 @@ For example: limits: - cpu: “2000m” + cpu: "2000m" memory: 4Gi requests: - cpu: “2000m” + cpu: "2000m" memory: 4Gi @@ -99,13 +99,13 @@ redisEnterpriseNodeResources: limits: - cpu: “8000m” + cpu: "8000m" memory: 30Gi requests - cpu: “8000m” + cpu: "8000m" memory: 30Gi diff --git a/content/operate/kubernetes/7.8.4/deployment/openshift/old-index.md b/content/operate/kubernetes/7.8.4/deployment/openshift/old-index.md index 26bba65874..9948291a18 100644 --- a/content/operate/kubernetes/7.8.4/deployment/openshift/old-index.md +++ b/content/operate/kubernetes/7.8.4/deployment/openshift/old-index.md @@ -38,7 +38,7 @@ Prerequisites: {{< image filename="/images/rs/getting-started-kubernetes-openshift-image1.png" >}} -- Click on “admin” (upper right corner) and then “Copy Login.” +- Click on "admin" (upper right corner) and then "Copy Login." {{< image filename="/images/rs/getting-started-kubernetes-openshift-image4.png" >}} @@ -89,7 +89,7 @@ Let’s look at each yaml file to see what requires editing: You should receive the following response: ```sh - securitycontextconstraints.security.openshift.io “redis-enterprise-scc” configured + securitycontextconstraints.security.openshift.io "redis-enterprise-scc" configured ``` Now you need to bind the scc to your project by typing: @@ -98,7 +98,7 @@ Let’s look at each yaml file to see what requires editing: oc adm policy add-scc-to-group redis-enterprise-scc system:serviceaccounts:your_project_name ``` - (If you do not remember your project name, run “oc project”) + (If you do not remember your project name, run "oc project") - [openshift.bundle.yaml](https://github.com/RedisLabs/redis-enterprise-k8s-docs/blob/master/openshift.bundle.yaml) - @@ -215,15 +215,15 @@ Now, run `kubectl get deployment` and verify that your redis-enterprise-operator This yaml can be edited to the required use case, however, the sample provided can be used for test/dev and quick start purposes. Here are the main fields you may review and edit: - - name: “your_cluster_name” (e.g. “demo-cluster”) + - name: "your_cluster_name" (e.g. "demo-cluster") - nodes: number_of_nodes_in_the_cluster (Must be an uneven number of at least 3 or greater—[here’s why](https://redislabs.com/redis-enterprise/technology/highly-available-redis/)) - uiServiceType: service_type Service type value can be either ClusterIP or LoadBalancer. This is an optional configuration based on [k8s service types](https://kubernetes.io/docs/tutorials/kubernetes-basics/expose/expose-intro/). The default is ClusterIP. - - storageClassName: “gp2“ + - storageClassName: "gp2" - This specifies the [StorageClass](https://kubernetes.io/docs/concepts/storage/storage-classes/) used for your nodes’ persistent disks. For example, AWS uses “gp2” as a default, GKE uses “standard” and Azure uses "default"). + This specifies the [StorageClass](https://kubernetes.io/docs/concepts/storage/storage-classes/) used for your nodes’ persistent disks. For example, AWS uses "gp2" as a default, GKE uses "standard" and Azure uses "default"). - redisEnterpriseNodeResources: The [compute resources](https://docs.openshift.com/enterprise/3.2/dev_guide/compute_resources.html#dev-compute-resources) required for each node. - limits – specifies the max resources for a Redis node @@ -233,11 +233,11 @@ Now, run `kubectl get deployment` and verify that your redis-enterprise-operator ```sh limits - cpu: “4000m” + cpu: "4000m" memory: 4Gi requests - cpu: “4000m” + cpu: "4000m" memory: 4Gi ``` @@ -250,10 +250,10 @@ Resource limits should equal requests ([Learn why](https://github.com/RedisLabs/ - serviceBrokerSpec – - enabled: \ - This specifies [persistence](https://redislabs.com/redis-features/persistence) for the Service Broker with an “enabled/disabled” flag. The default is “false.” + This specifies [persistence](https://redislabs.com/redis-features/persistence) for the Service Broker with an "enabled/disabled" flag. The default is "false." persistentSpec: - storageClassName: “gp2“ + storageClassName: "gp2" - redisEnterpriseImageSpec: This configuration controls the Redis Enterprise version used, and where it is fetched from. This is an optional field. The Operator will automatically use the matching RHEL image version for the release. @@ -272,7 +272,7 @@ Once you have your_cluster_name yaml set, you need to apply it to create your Re kubectl apply -f your_cluster_name.yaml ``` -Run kubectl get rec and verify that creation was successful (rec is a shortcut for “RedisEnterpriseClusters”). +Run kubectl get rec and verify that creation was successful (rec is a shortcut for "RedisEnterpriseClusters"). You should receive a response similar to the following: @@ -325,7 +325,7 @@ In order to create your database, we will log in to the Redis Enterprise UI. {{< image filename="/images/rs/getting-started-kubernetes-openshift-image5.png" >}} - In order to retrieve your password, navigate to the OpenShift management console, select your project name, go to Resources-\>Secrets-\>your_cluster_name -- Retrieve your password by selecting “Reveal Secret.” +- Retrieve your password by selecting "Reveal Secret." {{< warning >}} Do not change the default admin user password in the Redis Enterprise admin console. diff --git a/content/operate/kubernetes/7.8.4/faqs/_index.md b/content/operate/kubernetes/7.8.4/faqs/_index.md index be2cc9bd6d..9098cd35c3 100644 --- a/content/operate/kubernetes/7.8.4/faqs/_index.md +++ b/content/operate/kubernetes/7.8.4/faqs/_index.md @@ -114,7 +114,7 @@ metadata: kind: RedisEnterpriseCluster name: test uid: 8b247469-c715-11e8-a5d5-0a778671fc2e - resourceVersion: “911969” + resourceVersion: "911969" selfLink: /api/v1/namespaces/redis/secrets/redis-enterprise-cluster uid: 8c4ff52e-c715-11e8-80f5-02cc4fca9682 type: Opaque @@ -131,7 +131,7 @@ echo "Q2h5N1BBY28=" | base64 –-decode To retrieve your password, navigate to the OpenShift management console, select your project name, go to Resources->Secrets->your_cluster_name -Retrieve your password by selecting “Reveal Secret.” +Retrieve your password by selecting "Reveal Secret." {{< image filename="/images/rs/openshift-password-retrieval.png" >}} diff --git a/content/operate/kubernetes/7.8.4/recommendations/persistent-volumes.md b/content/operate/kubernetes/7.8.4/recommendations/persistent-volumes.md index f2b84974b4..d3427ab27e 100644 --- a/content/operate/kubernetes/7.8.4/recommendations/persistent-volumes.md +++ b/content/operate/kubernetes/7.8.4/recommendations/persistent-volumes.md @@ -29,7 +29,7 @@ spec should include a *persistentSpec* section, in the persistentSpec: enabled: true storageClassName: "standard" - volumeSize: "23Gi” #optional + volumeSize: "23Gi" #optional Persistence storage is a requirement for production deployments. @@ -71,7 +71,7 @@ deployment, use the following command: kubectl get StorageClass -Typically, AWS provides “gp2” as the Storage Class name while GKE uses “standard.” +Typically, AWS provides "gp2" as the Storage Class name while GKE uses "standard." Azure provides two Storage Classes: "default" using HDDs, and "managed-premium" using SSDs. Below is an example of a response to the command. @@ -101,8 +101,8 @@ Example of the redisEnterpriseNodeResources definition: redisEnterpriseNodeResources: limits: - cpu: “4000m” + cpu: "4000m" memory: 4Gi requests: - cpu: “4000m” + cpu: "4000m" memory: 4Gi diff --git a/content/operate/kubernetes/7.8.4/recommendations/sizing-on-kubernetes.md b/content/operate/kubernetes/7.8.4/recommendations/sizing-on-kubernetes.md index 9728d943fe..f8b9bad036 100644 --- a/content/operate/kubernetes/7.8.4/recommendations/sizing-on-kubernetes.md +++ b/content/operate/kubernetes/7.8.4/recommendations/sizing-on-kubernetes.md @@ -70,13 +70,13 @@ For example: limits: - cpu: “2000m” + cpu: "2000m" memory: 4Gi requests: - cpu: “2000m” + cpu: "2000m" memory: 4Gi @@ -99,13 +99,13 @@ redisEnterpriseNodeResources: limits: - cpu: “8000m” + cpu: "8000m" memory: 30Gi requests - cpu: “8000m” + cpu: "8000m" memory: 30Gi diff --git a/content/operate/kubernetes/7.8.6/deployment/openshift/old-index.md b/content/operate/kubernetes/7.8.6/deployment/openshift/old-index.md index 2507f37f26..cceda25630 100644 --- a/content/operate/kubernetes/7.8.6/deployment/openshift/old-index.md +++ b/content/operate/kubernetes/7.8.6/deployment/openshift/old-index.md @@ -38,7 +38,7 @@ Prerequisites: {{< image filename="/images/rs/getting-started-kubernetes-openshift-image1.png" >}} -- Click on “admin” (upper right corner) and then “Copy Login.” +- Click on "admin" (upper right corner) and then "Copy Login." {{< image filename="/images/rs/getting-started-kubernetes-openshift-image4.png" >}} @@ -89,7 +89,7 @@ Let’s look at each yaml file to see what requires editing: You should receive the following response: ```sh - securitycontextconstraints.security.openshift.io “redis-enterprise-scc” configured + securitycontextconstraints.security.openshift.io "redis-enterprise-scc" configured ``` Now you need to bind the scc to your project by typing: @@ -98,7 +98,7 @@ Let’s look at each yaml file to see what requires editing: oc adm policy add-scc-to-group redis-enterprise-scc system:serviceaccounts:your_project_name ``` - (If you do not remember your project name, run “oc project”) + (If you do not remember your project name, run "oc project") - [openshift.bundle.yaml](https://github.com/RedisLabs/redis-enterprise-k8s-docs/blob/master/openshift.bundle.yaml) - @@ -215,15 +215,15 @@ Now, run `kubectl get deployment` and verify that your redis-enterprise-operator This yaml can be edited to the required use case, however, the sample provided can be used for test/dev and quick start purposes. Here are the main fields you may review and edit: - - name: “your_cluster_name” (e.g. “demo-cluster”) + - name: "your_cluster_name" (e.g. "demo-cluster") - nodes: number_of_nodes_in_the_cluster (Must be an uneven number of at least 3 or greater—[here’s why](https://redislabs.com/redis-enterprise/technology/highly-available-redis/)) - uiServiceType: service_type Service type value can be either ClusterIP or LoadBalancer. This is an optional configuration based on [k8s service types](https://kubernetes.io/docs/tutorials/kubernetes-basics/expose/expose-intro/). The default is ClusterIP. - - storageClassName: “gp2“ + - storageClassName: "gp2" - This specifies the [StorageClass](https://kubernetes.io/docs/concepts/storage/storage-classes/) used for your nodes’ persistent disks. For example, AWS uses “gp2” as a default, GKE uses “standard” and Azure uses "default"). + This specifies the [StorageClass](https://kubernetes.io/docs/concepts/storage/storage-classes/) used for your nodes’ persistent disks. For example, AWS uses "gp2" as a default, GKE uses "standard" and Azure uses "default"). - redisEnterpriseNodeResources: The [compute resources](https://docs.openshift.com/enterprise/3.2/dev_guide/compute_resources.html#dev-compute-resources) required for each node. - limits – specifies the max resources for a Redis node @@ -233,11 +233,11 @@ Now, run `kubectl get deployment` and verify that your redis-enterprise-operator ```sh limits - cpu: “4000m” + cpu: "4000m" memory: 4Gi requests - cpu: “4000m” + cpu: "4000m" memory: 4Gi ``` @@ -250,10 +250,10 @@ Resource limits should equal requests ([Learn why](https://github.com/RedisLabs/ - serviceBrokerSpec – - enabled: \ - This specifies [persistence](https://redislabs.com/redis-features/persistence) for the Service Broker with an “enabled/disabled” flag. The default is “false.” + This specifies [persistence](https://redislabs.com/redis-features/persistence) for the Service Broker with an "enabled/disabled" flag. The default is "false." persistentSpec: - storageClassName: “gp2“ + storageClassName: "gp2" - redisEnterpriseImageSpec: This configuration controls the Redis Enterprise version used, and where it is fetched from. This is an optional field. The Operator will automatically use the matching RHEL image version for the release. @@ -272,7 +272,7 @@ Once you have your_cluster_name yaml set, you need to apply it to create your Re kubectl apply -f your_cluster_name.yaml ``` -Run kubectl get rec and verify that creation was successful (rec is a shortcut for “RedisEnterpriseClusters”). +Run kubectl get rec and verify that creation was successful (rec is a shortcut for "RedisEnterpriseClusters"). You should receive a response similar to the following: @@ -325,7 +325,7 @@ In order to create your database, we will log in to the Redis Enterprise UI. {{< image filename="/images/rs/getting-started-kubernetes-openshift-image5.png" >}} - In order to retrieve your password, navigate to the OpenShift management console, select your project name, go to Resources-\>Secrets-\>your_cluster_name -- Retrieve your password by selecting “Reveal Secret.” +- Retrieve your password by selecting "Reveal Secret." {{< warning >}} Do not change the default admin user password in the Redis Enterprise admin console. diff --git a/content/operate/kubernetes/7.8.6/recommendations/persistent-volumes.md b/content/operate/kubernetes/7.8.6/recommendations/persistent-volumes.md index 44addeff50..74645a3034 100644 --- a/content/operate/kubernetes/7.8.6/recommendations/persistent-volumes.md +++ b/content/operate/kubernetes/7.8.6/recommendations/persistent-volumes.md @@ -29,7 +29,7 @@ spec should include a *persistentSpec* section, in the persistentSpec: enabled: true storageClassName: "standard" - volumeSize: "23Gi” #optional + volumeSize: "23Gi" #optional Persistence storage is a requirement for production deployments. @@ -71,7 +71,7 @@ deployment, use the following command: kubectl get StorageClass -Typically, AWS provides “gp2” as the Storage Class name while GKE uses “standard.” +Typically, AWS provides "gp2" as the Storage Class name while GKE uses "standard." Azure provides two Storage Classes: "default" using HDDs, and "managed-premium" using SSDs. Below is an example of a response to the command. @@ -101,8 +101,8 @@ Example of the redisEnterpriseNodeResources definition: redisEnterpriseNodeResources: limits: - cpu: “4000m” + cpu: "4000m" memory: 4Gi requests: - cpu: “4000m” + cpu: "4000m" memory: 4Gi diff --git a/content/operate/kubernetes/7.8.6/recommendations/sizing-on-kubernetes.md b/content/operate/kubernetes/7.8.6/recommendations/sizing-on-kubernetes.md index eb0562f6d8..b7e6656c89 100644 --- a/content/operate/kubernetes/7.8.6/recommendations/sizing-on-kubernetes.md +++ b/content/operate/kubernetes/7.8.6/recommendations/sizing-on-kubernetes.md @@ -70,13 +70,13 @@ For example: limits: - cpu: “2000m” + cpu: "2000m" memory: 4Gi requests: - cpu: “2000m” + cpu: "2000m" memory: 4Gi @@ -99,13 +99,13 @@ redisEnterpriseNodeResources: limits: - cpu: “8000m” + cpu: "8000m" memory: 30Gi requests - cpu: “8000m” + cpu: "8000m" memory: 30Gi diff --git a/content/operate/kubernetes/7.8.6/reference/supported_k8s_distributions.md b/content/operate/kubernetes/7.8.6/reference/supported_k8s_distributions.md index 47a3c80962..c6695b035a 100644 --- a/content/operate/kubernetes/7.8.6/reference/supported_k8s_distributions.md +++ b/content/operate/kubernetes/7.8.6/reference/supported_k8s_distributions.md @@ -13,7 +13,7 @@ url: '/operate/kubernetes/7.8.6/reference/supported_k8s_distributions/' Each release of Redis Enterprise for Kubernetes is thoroughly tested against a set of Kubernetes distributions. The table below lists Redis Enterprise for Kubernetes versions and the Kubernetes distributions they support. -{{}}Each platform is tested with its default configuration, including storage, network, security, and container runtime components.”{{}} +{{}}Each platform is tested with its default configuration, including storage, network, security, and container runtime components."{{}} ✅ Supported – This distribution is supported for this version of Redis Enterprise Software for Kubernetes. diff --git a/content/operate/kubernetes/recommendations/persistent-volumes.md b/content/operate/kubernetes/recommendations/persistent-volumes.md index 92c2739db1..d621c7c0ef 100644 --- a/content/operate/kubernetes/recommendations/persistent-volumes.md +++ b/content/operate/kubernetes/recommendations/persistent-volumes.md @@ -28,7 +28,7 @@ spec should include a *persistentSpec* section, in the persistentSpec: enabled: true storageClassName: "standard" - volumeSize: "23Gi” #optional + volumeSize: "23Gi" #optional Persistence storage is a requirement for production deployments. @@ -70,7 +70,7 @@ deployment, use the following command: kubectl get StorageClass -Typically, AWS provides “gp2” as the Storage Class name while GKE uses “standard.” +Typically, AWS provides "gp2" as the Storage Class name while GKE uses "standard." Azure provides two Storage Classes: "default" using HDDs, and "managed-premium" using SSDs. Below is an example of a response to the command. @@ -100,8 +100,8 @@ Example of the redisEnterpriseNodeResources definition: redisEnterpriseNodeResources: limits: - cpu: “4000m” + cpu: "4000m" memory: 4Gi requests: - cpu: “4000m” + cpu: "4000m" memory: 4Gi diff --git a/content/operate/kubernetes/recommendations/sizing-on-kubernetes.md b/content/operate/kubernetes/recommendations/sizing-on-kubernetes.md index 156418f264..06cce995fb 100644 --- a/content/operate/kubernetes/recommendations/sizing-on-kubernetes.md +++ b/content/operate/kubernetes/recommendations/sizing-on-kubernetes.md @@ -69,13 +69,13 @@ For example: limits: - cpu: “2000m” + cpu: "2000m" memory: 4Gi requests: - cpu: “2000m” + cpu: "2000m" memory: 4Gi @@ -98,13 +98,13 @@ redisEnterpriseNodeResources: limits: - cpu: “8000m” + cpu: "8000m" memory: 30Gi requests - cpu: “8000m” + cpu: "8000m" memory: 30Gi diff --git a/content/operate/kubernetes/release-notes/7-22-0-releases/_index.md b/content/operate/kubernetes/release-notes/7-22-0-releases/_index.md index e02bba9dd5..9708c5a1bd 100644 --- a/content/operate/kubernetes/release-notes/7-22-0-releases/_index.md +++ b/content/operate/kubernetes/release-notes/7-22-0-releases/_index.md @@ -28,7 +28,7 @@ Redis Enterprise for Kubernetes 7.22.0 includes bug fixes, enhancements, and sup - **Missing endpoint for admission endpoint (rare) (RED-119469)** Restart the operator pod. -- **The REDB “redisVersion” field can’t be used for memcached databases(RED-119152)** +- **The REDB "redisVersion" field can’t be used for memcached databases(RED-119152)** - **When modifying the database suffix for an Active-Active database, while the service-rigger is in a terminating state, the services-rigger will delete and create the ingress or route resources in a loop (RED-107687)** Wait until the services rigger pod has finished to terminate it. diff --git a/content/operate/kubernetes/release-notes/7-4-2-releases/7-4-2-12.md b/content/operate/kubernetes/release-notes/7-4-2-releases/7-4-2-12.md index 47dadad62f..e7c7111900 100644 --- a/content/operate/kubernetes/release-notes/7-4-2-releases/7-4-2-12.md +++ b/content/operate/kubernetes/release-notes/7-4-2-releases/7-4-2-12.md @@ -113,7 +113,7 @@ Any distribution not listed below is not supported for production workloads. ### Existing limitations -- **The REDB “redisVersion” field can’t be used for memcached databases(RED-119152)** +- **The REDB "redisVersion" field can’t be used for memcached databases(RED-119152)** - **When modifying the database suffix for an Active-Active database, while the service-rigger is in a terminating state, the services-rigger will delete and create the ingress or route resources in a loop (RED-107687)** Wait until the services rigger pod has finished to terminate it. diff --git a/content/operate/kubernetes/release-notes/7-4-2-releases/_index.md b/content/operate/kubernetes/release-notes/7-4-2-releases/_index.md index ef7a84f2d0..ce645a2995 100644 --- a/content/operate/kubernetes/release-notes/7-4-2-releases/_index.md +++ b/content/operate/kubernetes/release-notes/7-4-2-releases/_index.md @@ -77,7 +77,7 @@ The limitations below are specific to the Redis Enterprise for Kubernetes produc ### New limitations - **Missing endpoint for admission endpoint (rare) (RED-119469)** Restart the operator pod. -- **The REDB “redisVersion” field can’t be used for memcached databases(RED-119152)** +- **The REDB "redisVersion" field can’t be used for memcached databases(RED-119152)** ### Existing limitations diff --git a/content/operate/kubernetes/release-notes/7-4-6-releases/7-4-6-2.md b/content/operate/kubernetes/release-notes/7-4-6-releases/7-4-6-2.md index 1a560ac7fe..59b2e969bc 100644 --- a/content/operate/kubernetes/release-notes/7-4-6-releases/7-4-6-2.md +++ b/content/operate/kubernetes/release-notes/7-4-6-releases/7-4-6-2.md @@ -100,7 +100,7 @@ Any distribution not listed below is not supported for production workloads. - **Missing endpoint for admission endpoint (rare) (RED-119469)** Restart the operator pod. -- **The REDB “redisVersion” field can’t be used for memcached databases(RED-119152)** +- **The REDB "redisVersion" field can’t be used for memcached databases(RED-119152)** - **PVC expansion is not supported when using Redis on Flash (Auto Tiering) (RED-165770)** Do not enable `enablePersistentVolumeResize` if your REC uses `redisOnFlashSpec` as this will result in conflicts. diff --git a/content/operate/kubernetes/release-notes/7-4-6-releases/_index.md b/content/operate/kubernetes/release-notes/7-4-6-releases/_index.md index c752962fea..782a92029a 100644 --- a/content/operate/kubernetes/release-notes/7-4-6-releases/_index.md +++ b/content/operate/kubernetes/release-notes/7-4-6-releases/_index.md @@ -67,7 +67,7 @@ Any distribution not listed below is not supported for production workloads. - **Missing endpoint for admission endpoint (rare) (RED-119469)** Restart the operator pod. -- **The REDB “redisVersion” field can’t be used for memcached databases(RED-119152)** +- **The REDB "redisVersion" field can’t be used for memcached databases(RED-119152)** - **When modifying the database suffix for an Active-Active database, while the service-rigger is in a terminating state, the services-rigger will delete and create the ingress or route resources in a loop (RED-107687)** Wait until the services rigger pod has finished to terminate it. diff --git a/content/operate/kubernetes/release-notes/7-8-2-releases/7-8-2-6-nov24.md b/content/operate/kubernetes/release-notes/7-8-2-releases/7-8-2-6-nov24.md index aacd7036b1..f0099c6a08 100644 --- a/content/operate/kubernetes/release-notes/7-8-2-releases/7-8-2-6-nov24.md +++ b/content/operate/kubernetes/release-notes/7-8-2-releases/7-8-2-6-nov24.md @@ -112,7 +112,7 @@ Any distribution not listed below is not supported for production workloads. - **Missing endpoint for admission endpoint (rare) (RED-119469)** Restart the operator pod. -- **The REDB “redisVersion” field can’t be used for memcached databases(RED-119152)** +- **The REDB "redisVersion" field can’t be used for memcached databases(RED-119152)** - **PVC expansion is not supported when using Redis on Flash (Auto Tiering) (RED-165770)** Do not enable `enablePersistentVolumeResize` if your REC uses `redisOnFlashSpec` as this will result in conflicts. diff --git a/content/operate/kubernetes/release-notes/7-8-2-releases/_index.md b/content/operate/kubernetes/release-notes/7-8-2-releases/_index.md index 71fe07d36e..ffb531bd2c 100644 --- a/content/operate/kubernetes/release-notes/7-8-2-releases/_index.md +++ b/content/operate/kubernetes/release-notes/7-8-2-releases/_index.md @@ -46,7 +46,7 @@ See [Upgrade Redis Enterprise for Kubernetes]({{