Skip to content

Commit 881877e

Browse files
author
mmahipal
committed
Update README.md to remove Operator Image Pull Secrets
1 parent 76832ee commit 881877e

File tree

2 files changed

+3
-22
lines changed

2 files changed

+3
-22
lines changed

README.md

Lines changed: 1 addition & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -49,17 +49,6 @@ Oracle strongly recommends that you ensure your system meets the following [Prer
4949
kubectl apply -f https://github.com/jetstack/cert-manager/releases/latest/download/cert-manager.yaml
5050
```
5151

52-
* ### Create Operator Image Pull Secrets
53-
54-
Sign into [https://container-registry.oracle.com/](https://container-registry.oracle.com/) and accept the license agreement for the Operator image.
55-
56-
Create an image pull secret for Oracle Container Registry:
57-
58-
```sh
59-
kubectl create namespace oracle-database-operator-system
60-
kubectl create secret docker-registry container-registry-secret -n oracle-database-operator-system --docker-server=container-registry.oracle.com --docker-username='<oracle-sso-email-address>' --docker-password='<oracle-sso-password>' --docker-email='<oracle-sso-email-address>'
61-
```
62-
6352
## Quick Install of the Operator
6453

6554
To install the operator in the cluster quickly, you can use a single [oracle-database-operator.yaml](https://github.com/oracle/oracle-database-operator/blob/main/oracle-database-operator.yaml) file. Operator pod replicas are set to a default of 3 for High Availability, which can be scaled up and down.
@@ -120,7 +109,7 @@ YAML file templates are available under [`/config/samples`](./config/samples/).
120109

121110
Note: If the CRD instances are not deleted, and the operator is deleted by using the preceding command, then operator deployment and instance objects (pods,services,PVCs, and so on) are deleted. However, the CRD deletion stops responding, because the CRD instances have finalizers that can only be removed by the operator pod, which is deleted when the APIServices are deleted.
122111

123-
* ### Retain the CRDs and APIservices
112+
* ### Retaining the CRDs and APIservices
124113

125114
To delete the operator deployment and retain the CRDs, run the following commands:
126115

doc/installation/OPERATOR_INSTALLATION_README.md

Lines changed: 2 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -57,17 +57,9 @@ If you encounter an issue with these steps, then refer to the more detailed step
5757
Clone the [oracle-database-operator](https://github.com/oracle/oracle-database-operator) on your local machine
5858

5959
## Review and modify the Cloned Repository
60-
Make changes as needed to the repository.
60+
Make changes as needed to the repository.
6161

62-
If you want to run the operator locally outside the cluster, then run the following steps:
63-
64-
```sh
65-
cd oracle-database-operator
66-
make generate
67-
make manifests
68-
make install run
69-
```
70-
If you want to run the operator inside the cluster, then run the following steps:
62+
## Build and push the Operator image
7163

7264
```sh
7365
cd oracle-database-operator

0 commit comments

Comments
 (0)