|
| 1 | +Crunchy Data PostgreSQL Operator |
| 2 | +======= |
| 3 | + |
| 4 | +[PostgreSQL](https://postgresql.org) is a powerful, open source object-relational database system. It has more than 15 years of active development and a proven architecture that has earned it a strong reputation for reliability, data integrity, and correctness. |
| 5 | + |
| 6 | + |
| 7 | +TL;DR; |
| 8 | +------ |
| 9 | + |
| 10 | +```console |
| 11 | +$ helm install --name postgres-operator --namespace=postgres-operator postgres-operator |
| 12 | +``` |
| 13 | + |
| 14 | +Introduction |
| 15 | +------------ |
| 16 | + |
| 17 | +This chart bootstraps a PostgreSQL Operator. |
| 18 | + |
| 19 | +The PostgreSQL Operator provides a Kubernetes operator capability for managing PostgreSQL Clusters deployed within a Kubernetes. |
| 20 | +The PostgreSQL Operator leverages Kubernetes Third Party Resources to define custom resource types such as: |
| 21 | + |
| 22 | + * *pgcluster* |
| 23 | + * *pgbackups* |
| 24 | + * *pgupgrades* |
| 25 | + * *pgclones* |
| 26 | + * *pgpolicies* |
| 27 | + * *pgpolicylogs* |
| 28 | + |
| 29 | + |
| 30 | +Once those custom objects are defined, Kubernetes provides the ability to create and manage those objects similar to any other native Kubernetes object. |
| 31 | + |
| 32 | +The PostgreSQL Operator runs within Kubernetes detecting these new custom object types being created, updated, or removed. |
| 33 | + |
| 34 | +Once the objects are detected, the PostgreSQL Operator enables users to perform operations across the Kubernetes environment, including: |
| 35 | + |
| 36 | +* Create a PostgreSQL Cluster |
| 37 | +* Destroy a PostgreSQL Cluster |
| 38 | +* Backup a PostgreSQL Cluster |
| 39 | +* Scale a a PostgreSQL Cluster |
| 40 | +* Restore a PostgreSQL Cluster |
| 41 | +* Upgrade a PostgreSQL Cluster |
| 42 | +* View PVC |
| 43 | +* Test Connections to a PostgreSQL Cluster |
| 44 | +* Clone a PostgreSQL Cluster |
| 45 | +* Create a SQL-based Policy |
| 46 | +* Apply a SQL-based Policy to a PostgreSQL Cluster |
| 47 | +* Perform User Management |
| 48 | +* Apply User Defined Labels to PostgreSQL Clusters |
| 49 | +* Perform Password Management |
| 50 | + |
| 51 | +What actually gets created on the Kube cluster for a |
| 52 | +*pgcluster* resource is defined as a *deployment strategy*. Strategies |
| 53 | +are documented in detail in [Deployment Strategies](https://github.com/CrunchyData/postgres-operator/blob/master/docs/design.asciidoc#postgresql-operator-deployment-strategies). |
| 54 | + |
| 55 | + |
| 56 | +Installing the Chart |
| 57 | +-------------------- |
| 58 | + |
| 59 | +The chart can be installed as follows: |
| 60 | + |
| 61 | +```console |
| 62 | +$ helm install postgres-operator --name postgres-operator --namespace=postgres-operator |
| 63 | +``` |
| 64 | + |
| 65 | +The command deploys postgres-operator on the Kubernetes cluster in the default configuration. |
| 66 | + |
| 67 | +> **Tip**: List all releases using `helm list` |
| 68 | +
|
| 69 | +Uninstalling the Chart |
| 70 | +---------------------- |
| 71 | + |
| 72 | +To uninstall/delete the `postgres-operator` deployment: |
| 73 | + |
| 74 | +```console |
| 75 | +$ helm delete postgres-operator |
| 76 | +``` |
| 77 | + |
| 78 | +The command removes all the Kubernetes components associated with the chart and deletes the release. |
| 79 | + |
| 80 | +Configuration |
| 81 | +------------- |
| 82 | + |
| 83 | +See `values.yaml` for configuration notes. Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example, |
| 84 | + |
| 85 | +```console |
| 86 | +$ helm install postgres-operator --name postgres-operator --namespace=postgres-operator \ |
| 87 | + --set env.debug=false |
| 88 | +``` |
| 89 | + |
| 90 | +The above command disables the debugging. |
| 91 | + |
| 92 | +Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example, |
| 93 | + |
| 94 | +```console |
| 95 | +$ helm install postgres-operator --name postgres-operator --namespace=postgres-operator \ |
| 96 | + -f values.yaml |
| 97 | +``` |
| 98 | + |
| 99 | +> **Tip**: You can use the default [values.yaml](values.yaml) |
0 commit comments