Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

typo fix #211

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

typo fix #211

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
8 changes: 4 additions & 4 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -104,7 +104,7 @@ This is the fastest way to get up and running with a new Redis Enterprise on Kub
```
> Note: Once the cluster is up, the cluster GUI and API could be used to configure databases. It is recommended to use the K8s REDB API that is configured through the following steps. To configure the cluster using the cluster GUI/API, use the ui service created by the operator and the default credentials as set in a secret. The secret name is the same as the cluster name within the namespace.
5. Redis Enterprise Database (REDB) Admission Controller:
The Admission Controlller is recommended for use. It uses the Redis Enterprise Cluster to dynamically validate that REDB resources as configured by the operator are valid.
The Admission Controller is recommended for use. It uses the Redis Enterprise Cluster to dynamically validate that REDB resources as configured by the operator are valid.
Steps to configure the Admission Controller:
> **Note:** Redis Labs' Redis Enterprise Operator can also be installed through the [Gesher Admission Proxy](admission/GESHER.md)
* Wait for the secret to be created:
Expand Down Expand Up @@ -172,7 +172,7 @@ This is the fastest way to get up and running with a new Redis Enterprise on Kub
```
<a name="verify_admission_installation"></a>
* Verify the installation
In order to verify that the all the components of the Admission Controller are installed correctly, we will try to apply an invalid resource that should force the admission controller to reject it. If it applies succesfully, it means the admission controller has not been hooked up correctly.
In order to verify that the all the components of the Admission Controller are installed correctly, we will try to apply an invalid resource that should force the admission controller to reject it. If it applies successfully, it means the admission controller has not been hooked up correctly.

```shell script
$ kubectl apply -f - << EOF
Expand Down Expand Up @@ -264,7 +264,7 @@ That folder also contains the custom resource definitions compatible with OpenSh
oc apply -f openshift/rec_rhel.yaml
```
6. Redis Enterprise Database (REDB) Admission Controller:
The Admission Controlller is recommended for use. It uses the Redis Enterprise Cluster to dynamically validate that REDB resources as configured by the operator are valid.
The Admission Controller is recommended for use. It uses the Redis Enterprise Cluster to dynamically validate that REDB resources as configured by the operator are valid.
Steps to configure the Admission Controller:
* Wait for the secret to be created by the operator bundle deployment
```shell script
Expand Down Expand Up @@ -326,7 +326,7 @@ That folder also contains the custom resource definitions compatible with OpenSh
```
<a name="verify_admission_installation_openshift"></a>
* Verify the installation
In order to verify that the all the components of the Admission Controller are installed correctly, we will try to apply an invalid resource that should force the admission controller to reject it. If it applies succesfully, it means the admission controller has not been hooked up correctly.
In order to verify that the all the components of the Admission Controller are installed correctly, we will try to apply an invalid resource that should force the admission controller to reject it. If it applies successfully, it means the admission controller has not been hooked up correctly.

```shell script
$ oc apply -f - << EOF
Expand Down