Skip to content

Removed Operator Image Pull Secrets section in README.md #2

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

Merged
merged 2 commits into from
Oct 26, 2021
Merged

Removed Operator Image Pull Secrets section in README.md #2

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
881877e
Update README.md to remove Operator Image Pull Secrets
Oct 26, 2021
13ef867
Revernt changes to Operator Installation
Oct 26, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 1 addition & 12 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -49,17 +49,6 @@ Oracle strongly recommends that you ensure your system meets the following [Prer
kubectl apply -f https://github.com/jetstack/cert-manager/releases/latest/download/cert-manager.yaml
```

* ### Create Operator Image Pull Secrets

Sign into [https://container-registry.oracle.com/](https://container-registry.oracle.com/) and accept the license agreement for the Operator image.

Create an image pull secret for Oracle Container Registry:

```sh
kubectl create namespace oracle-database-operator-system
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>'
```

## Quick Install of the Operator

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.
Expand Down Expand Up @@ -120,7 +109,7 @@ YAML file templates are available under [`/config/samples`](./config/samples/).

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.

* ### Retain the CRDs and APIservices
* ### Retaining the CRDs and APIservices

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

Expand Down