You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: README.md
+37-18
Original file line number
Diff line number
Diff line change
@@ -5,15 +5,16 @@
5
5
*[Prerequisites](#prerequisites)
6
6
*[Deployment](#deployment)
7
7
*[Configuration Options](#configuration)
8
+
*[IPV4 enforcement](#ipv4-enforcement)
8
9
9
10
10
11
11
12
#### Prerequisites:
12
-
* A minimum of 3 nodes which support the following [requirements][]
13
+
* A minimum of 3 nodes which support the following [requirements][]
13
14
* A kubernetes version of 1.8 or higher
14
15
* For service broker - a k8s distribution that supports service catalog (see also: [service-catalog][])
15
-
> Note: For RHEL based images and/or deployments on OpenShift, please use redis-enterprise-cluster_rhel.yaml and operator_rhel.yaml.
16
-
For Service Broker, please see examples/with_service_broker_rhel.yaml. RedHat certified images are available on: https://access.redhat.com/containers/#/product/71f6d1bb3408bd0d
16
+
> Note: For RHEL based images and/or deployments on OpenShift, please use redis-enterprise-cluster_rhel.yaml and operator_rhel.yaml.
17
+
For Service Broker, please see examples/with_service_broker_rhel.yaml. RedHat certified images are available on: https://access.redhat.com/containers/#/product/71f6d1bb3408bd0d
cluster role "redis-enterprise-operator-sb" added: "redis-enterprise-operator"
68
69
```
69
70
70
-
3) The next step applies rbac.yaml, creating a service account, role, and role-binding to allow resources access control (provides permissions to create and manage resources):
71
+
3) You can optionally use pod security policy.
72
+
```
73
+
kubectl apply -f psp.yaml
74
+
```
75
+
If you use this option, you should add the policy name to REC configuration, in redis-enterprise-cluster.yaml.
76
+
```
77
+
podSecurityPolicyName: "redis-enterprise-psp"
78
+
```
79
+
80
+
81
+
4) The next step applies rbac.yaml, creating a service account, role, and role-binding to allow resources access control (provides permissions to create and manage resources):
5) Create the operator deployment: a deployment responsible for managing the k8s deployment and lifecycle of a redis-enterprise-cluster.
102
+
6) Create the operator deployment: a deployment responsible for managing the k8s deployment and lifecycle of a redis-enterprise-cluster.
92
103
Among many other responsibilities, it creates a stateful set that runs the redis enterprise nodes (as pods).
93
-
104
+
94
105
Before applying - edit the tag according to the relevant operator version: ```image: redislabs/operator:tag```
95
106
```
96
107
kubectl apply -f operator.yaml
97
108
```
98
-
109
+
99
110
> You should receive the following response:
100
111
```
101
112
deployment.apps/redis-enterprise-operator created
102
113
```
103
114
104
-
6) Run ```kubectl get Deployment``` and verify redis-enterprise-operator deployment is running
115
+
7) Run ```kubectl get Deployment``` and verify redis-enterprise-operator deployment is running
105
116
106
117
A typical response may look like this:
107
118
```
@@ -110,12 +121,12 @@ This creates another API resource to be handled by the k8s API server and manage
110
121
|redis-enterprise-operator|1 | 1 | 1 | 1 | 2m |
111
122
```
112
123
113
-
7) Create A Redis Enterprise Cluster:
124
+
8) Create A Redis Enterprise Cluster:
114
125
Choose the configuration relevant for you (see next section) - you may find additional examples in the examples folder. Note that you need to specify an image tag if you'd like to pull a RHEL image.
0 commit comments