diff --git a/README.md b/README.md index 75187b0..49365b7 100644 --- a/README.md +++ b/README.md @@ -32,9 +32,9 @@ High level architecture and overview of the solution can be found [HERE](https:/ The following are the images and tags for this release: | Component | k8s | Openshift | | --- | --- | --- | -| Redis Enterprise | `redislabs/redis:6.2.4-55` | `redislabs/redis:6.2.4-55.rhel7-openshift` | -| Operator | `redislabs/operator:6.2.4-1` | `redislabs/operator:6.2.4-1` | -| Services Rigger | `redislabs/k8s-controller:6.2.4-1` | `redislabs/k8s-controller:6.2.4-1` | +| Redis Enterprise | `redislabs/redis:6.2.8-41` | `redislabs/redis:6.2.8-41.rhel7-openshift` | +| Operator | `redislabs/operator:6.2.8-2` | `redislabs/operator:6.2.8-2` | +| Services Rigger | `redislabs/k8s-controller:6.2.8-2` | `redislabs/k8s-controller:6.2.8-2` | > * RedHat certified images are available on [Redhat Catalog](https://access.redhat.com/containers/#/product/71f6d1bb3408bd0d)
@@ -114,11 +114,12 @@ This is the fastest way to get up and running with a new Redis Enterprise on Kub * Enable the Kubernetes webhook using the generated certificate **NOTE**: One must replace REPLACE_WITH_NAMESPACE in the following command with the namespace the REC was installed into. - + * Save the certificate into a local environmental variable ```shell script - # save cert CERT=`kubectl get secret admission-tls -o jsonpath='{.data.cert}'` - # create patch file + ``` + * Create a patch file + ```shell script sed 's/NAMESPACE_OF_SERVICE_ACCOUNT/REPLACE_WITH_NAMESPACE/g' admission/webhook.yaml | kubectl create -f - cat > modified-webhook.yaml < - In case you have several REC objects on your K8S cluster you need to limit the webhook to the relevant namespace. - This is done by adding a `namespaceSelector` to the webhook spec that targets a label found on the namespace.
- First, make sure you have such a relevant label on the namespace and that it is unique for this namespace. e.g. - ``` - apiVersion: v1 - kind: Namespace - metadata: - labels: - namespace-name: staging - name: staging - ``` - Then patch the webhook with a namespaceSelector. See this example: - ``` + * Limiting the webhook to the relevant namespaces: + Unless limited, webhooks will intercept requests from all namespaces.
+ In case you have several REC objects on your K8S cluster you need to limit the webhook to the relevant namespace. + This is done by adding a `namespaceSelector` to the webhook spec that targets a label found on the namespace.
+ + * First, make sure you have such a relevant label on the namespace and that it is unique for this namespace. e.g. + + ```yaml + apiVersion: v1 + kind: Namespace + metadata: + labels: + namespace-name: staging + name: staging + ``` + + * Then, patch the webhook with a namespaceSelector. See this example: + ```shell script cat > modified-webhook.yaml <