#### PostgreSQL Operator Installer

For existing PostgreSQL Operator deployments that were installed using the PostgreSQL Operator Installer, you will check out the appropriate release tag and update your the new configuration files. After this, you will need to update your Operator installation using the `DEPLOY_ACTION` method described in the [Configuring to Update and Uninstall](https://access.crunchydata.com/documentation/postgres-operator/4.6.2/installation/postgres-operator#configuring-to-update-and-uninstall) section of the documentation.

Please note, you will need to ensure that you have executed the [post-installation cleanup](https://access.crunchydata.com/documentation/postgres-operator/4.6.2/installation/postgres-operator#post-installation) between each `DEPLOY_ACTION` activity.


## Quickstart

If you believe that all the default settings in the installation manifest work for you, you can take a chance by running the manifest directly from the repository:

```
kubectl create namespace pgo
kubectl apply -f https://raw.githubusercontent.com/CrunchyData/postgres-operator/v4.6.2/installers/kubectl/postgres-operator.yml
```

However, we still advise that you read onward to see how to properly configure the PostgreSQL Operator.

#### Configuring to Update and Uninstall

The deploy job can be used to perform different deployment actions for the PostgreSQL Operator. When you run the job it will install the operator by default but you can change the deployment action to uninstall or update. The `DEPLOY_ACTION` environment variable in the `postgres-operator.yml` file can be set to `install`, `update`, and `uninstall`.