Skip to content

Commit 2fa7f2f

Browse files
kaitlynmichaelkaitlynmichael
committed
formatting edits
1 parent ed060b1 commit 2fa7f2f

File tree

3 files changed

+57
-54
lines changed

3 files changed

+57
-54
lines changed

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

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -58,12 +58,16 @@ Redis Enterprise Active-Active database (REAADB) contains a link to the RERC for
5858

5959
For a full list of fields and options, see the [REAADB API reference]({{<relref "/operate/kubernetes/reference/api/redis_enterprise_active_active_database_api">}}).
6060

61+
For examples, see the [YAML examples]({{< relref "/operate/kubernetes/reference/yaml/active-active" >}}) section.
62+
6163
### RERC custom resource
6264

6365
Redis Enterprise remote cluster (RERC) custom resource contains configuration details for all the participating clusters.
6466

6567
For a full list of fields and options, see the [RERC API reference]({{<relref "/operate/kubernetes/reference/api/redis_enterprise_remote_cluster_api">}}).
6668

69+
For examples, see the [YAML examples]({{< relref "/operate/kubernetes/reference/yaml/active-active" >}}) section.
70+
6771
### Limitations
6872

6973
* Existing Redis databases cannot be migrated to a REAADB. (DOC-3594)

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

Lines changed: 50 additions & 51 deletions
Original file line numberDiff line numberDiff line change
@@ -33,92 +33,91 @@ To create an Active-Active database, make sure you've completed all the followin
3333

3434
For a list of example values used throughout this article, see the [Example values](#example-values) section.
3535

36-
## Create `RedisEnterpriseRemoteCluster` resources {#create-rerc}
36+
## Create RERC custom resources {#create-rerc}
3737

3838
1. Create a `RedisEnterpriseRemoteCluster` (RERC) custom resource file for each participating Redis Enterprise cluster (REC).
3939

40-
Below are examples of RERC resources for two participating clusters. Substitute your own values to create your own resource.
40+
Below are examples of RERC resources for two participating clusters. Substitute your own values to create your own resource.
4141

42-
Example RERC (`rerc-ohare`) for the REC named `rec-chicago` in the namespace `ns-illinois`:
42+
Example RERC (`rerc-ohare`) for the REC named `rec-chicago` in the namespace `ns-illinois`:
4343

44-
{{<embed-yaml "k8s/rerc-ohare.md" "rerc-ohare.yaml">}}
44+
{{<embed-yaml "k8s/rerc-ohare.md" "rerc-ohare.yaml">}}
4545

46-
Example RERC (`rerc-raegan`) for the REC named `rec-arlington` in the namespace `ns-virginia`:
46+
Example RERC (`rerc-raegan`) for the REC named `rec-arlington` in the namespace `ns-virginia`:
4747

48-
{{<embed-yaml "k8s/rerc-raegan.md" "rerc-raegan.yaml">}}
48+
{{<embed-yaml "k8s/rerc-raegan.md" "rerc-raegan.yaml">}}
4949

50-
For more details on RERC fields, see the [RERC API reference]({{<relref "/operate/kubernetes/reference/api/redis_enterprise_remote_cluster_api">}}).
50+
For more details on RERC fields, see the [RERC API reference]({{<relref "/operate/kubernetes/reference/api/redis_enterprise_remote_cluster_api">}}).
5151

52-
1. Create a Redis Enterprise remote cluster from each RERC custom resource file.
52+
2. Create a Redis Enterprise remote cluster from each RERC custom resource file.
5353

54-
```sh
55-
kubectl create -f <rerc-file>
56-
```
54+
```sh
55+
kubectl create -f <rerc-file>
56+
```
5757

58-
1. Check the status of your RERC. If `STATUS` is `Active` and `SPEC STATUS` is `Valid`, then your configurations are correct.
58+
3. Check the status of your RERC. If `STATUS` is `Active` and `SPEC STATUS` is `Valid`, then your configurations are correct.
5959

60-
```sh
61-
kubectl get rerc <rerc-name>
62-
```
60+
```sh
61+
kubectl get rerc <rerc-name>
62+
```
6363

64-
The output should look similar to:
64+
The output should look similar to:
6565

66-
```sh
67-
kubectl get rerc rerc-ohare
66+
```sh
67+
kubectl get rerc rerc-ohare
6868

69-
NAME STATUS SPEC STATUS LOCAL
70-
rerc-ohare Active Valid true
71-
```
69+
NAME STATUS SPEC STATUS LOCAL
70+
rerc-ohare Active Valid true
71+
```
7272

73-
In case of errors, review the RERC custom resource events and the Redis Enterprise operator logs.
73+
In case of errors, review the RERC custom resource events and the Redis Enterprise operator logs.
7474

75-
## Create `RedisEnterpriseActiveActiveDatabase` resource {#create-reaadb}
75+
## Create the REAADB {#create-reaadb}
7676

7777
1. Create a `RedisEnterpriseActiveActiveDatabase` (REAADB) custom resource file meeting the naming requirements and listing the names of the RERC custom resources created in the last step.
7878

79-
Naming requirements:
80-
* less than 63 characters
81-
* contains only lowercase letters, numbers, or hyphens
82-
* starts with a letter
83-
* ends with a letter or digit
79+
Naming requirements:
80+
* less than 63 characters
81+
* contains only lowercase letters, numbers, or hyphens
82+
* starts with a letter
83+
* ends with a letter or digit
8484

85-
Example REAADB named `reaadb-boeing` linked to the REC named `rec-chicago` with two participating clusters and a global database configuration with shard count set to 3:
85+
Example REAADB named `reaadb-boeing` linked to the REC named `rec-chicago` with two participating clusters and a global database configuration with shard count set to 3:
8686

87-
{{<embed-yaml "k8s/reaadb-boeing.md" "reaadb-boeing.yaml">}}
87+
{{<embed-yaml "k8s/reaadb-boeing.md" "reaadb-boeing.yaml">}}
8888

89-
{{<note>}}Sharding is disabled on Active-Active databases created with a `shardCount` of 1. Sharding cannot be enabled after database creation. {{</note>}}
89+
{{<note>}}Sharding is disabled on Active-Active databases created with a `shardCount` of 1. Sharding cannot be enabled after database creation. {{</note>}}
9090

91-
For more details on RERC fields, see the [RERC API reference]({{<relref "/operate/kubernetes/reference/api/redis_enterprise_remote_cluster_api">}}).
91+
For more details on RERC fields, see the [RERC API reference]({{<relref "/operate/kubernetes/reference/api/redis_enterprise_remote_cluster_api">}}).
9292

93-
1. Create a Redis Enterprise Active-Active database from the REAADB custom resource file.
93+
2. Create a Redis Enterprise Active-Active database from the REAADB custom resource file.
9494

95-
```sh
96-
kubectl create -f <reaadb-file>
97-
```
95+
```sh
96+
kubectl create -f <reaadb-file>
97+
```
9898

99-
1. Check the status of your RERC. If `STATUS` is `Active` and `SPEC STATUS` is `Valid`, your configurations are correct.
99+
3. Check the status of your RERC. If `STATUS` is `Active` and `SPEC STATUS` is `Valid`, your configurations are correct.
100100

101-
```sh
102-
kubectl get reaadb <reaadb-name>
103-
```
101+
```sh
102+
kubectl get reaadb <reaadb-name>
103+
```
104104

105-
The output should look similar to:
105+
The output should look similar to:
106106

107-
```sh
108-
kubectl get reaadb reaadb-boeing
109-
110-
NAME STATUS SPEC STATUS LINKED REDBS REPLICATION STATUS
111-
reaadb-boeing active Valid up
112-
```
107+
```sh
108+
kubectl get reaadb reaadb-boeing
113109

110+
NAME STATUS SPEC STATUS LINKED REDBS REPLICATION STATUS
111+
reaadb-boeing active Valid up
112+
```
114113

115-
In case of errors, review the REAADB custom resource events and the Redis Enterprise operator logs.
114+
In case of errors, review the REAADB custom resource events and the Redis Enterprise operator logs.
116115

117116
## Example values
118117

119-
This article uses the following example values:
118+
This article uses the example values listed below. They can also be found in the [YAML examples]({{< relref "/operate/kubernetes/reference/yaml/active-active" >}}) section.
120119

121-
#### Example cluster 1
120+
Example cluster 1:
122121

123122
* REC name: `rec-chicago`
124123
* REC namespace: `ns-illinois`
@@ -127,7 +126,7 @@ This article uses the following example values:
127126
* API FQDN: `api-rec-chicago-ns-illinois.example.com`
128127
* DB FQDN suffix: `-db-rec-chicago-ns-illinois.example.com`
129128

130-
#### Example cluster 2
129+
Example cluster 2:
131130

132131
* REC name: `rec-arlington`
133132
* REC namespace: `ns-virginia`

‎content/operate/kubernetes/active-active/prepare-clusters.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -122,9 +122,9 @@ Now you are ready to [create your Redis Enterprise Active-Active database]({{< r
122122

123123
## Example values
124124

125-
This article uses the following example values:
125+
This article uses the example values listed below. They can also be found in the [YAML examples]({{< relref "/operate/kubernetes/reference/yaml/active-active" >}}) section.
126126

127-
#### Example cluster 1
127+
Example cluster 1:
128128

129129
* REC name: `rec-chicago`
130130
* REC namespace: `ns-illinois`
@@ -133,7 +133,7 @@ This article uses the following example values:
133133
* API FQDN: `api-rec-chicago-ns-illinois.example.com`
134134
* DB FQDN suffix: `-db-rec-chicago-ns-illinois.example.com`
135135

136-
#### Example cluster 2
136+
Example cluster 2:
137137

138138
* REC name: `rec-arlington`
139139
* REC namespace: `ns-virginia`

0 commit comments

Comments
 (0)