public_git
/
postgres-operator
mirror of https://github.com/zalando/postgres-operator.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Fix typos.

This commit is contained in:
Oleksii Kliukin 2017-04-03 15:53:08 +02:00 committed by Murat Kabilov
parent 7c45059fe8
commit 23f2bee362
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
README.md
View File

@ -1,16 +1,16 @@
# postgres operator prototype (WIP) # postgres operator prototype (WIP)
Postgres operator manages Postgres clustes in Kubernetes using the [operator pattern](https://coreos.com/blog/introducing-operators.html) Postgres operator manages Postgres clusters in Kubernetes using the [operator pattern](https://coreos.com/blog/introducing-operators.html)
During the initial run it registers the [third-party-resource (TPR)](https://kubernetes.io/docs/user-guide/thirdpartyresources/) for Postgres. During the initial run it registers the [third-party-resource (TPR)](https://kubernetes.io/docs/user-guide/thirdpartyresources/) for Postgres.
The Postgres TPR is essentially a schema that describes the contents of the manifests for deploying individual clusters. The Postgres TPR is essentially a schema that describes the contents of the manifests for deploying individual clusters.
One the operator is running, it performs the following actions: Once the operator is running, it performs the following actions:
* watches for new cluster postgres manifests and deploys corresponding clusters. * watches for new postgres cluster manifests and deploys corresponding clusters.
* watches for updates to existing manifests and changes corresponding properties of the running clusters. * watches for updates to existing manifests and changes corresponding properties of the running clusters.
* watches for deletes of the existing manifests and deletes corresponding database clusters. * watches for deletes of the existing manifests and deletes corresponding database clusters.
* acts on an update to the operator definition itself and changes the running clusters when necessary (i.e. when the docker image inside the operator definition has been updated.) * acts on an update to the operator definition itself and changes the running clusters when necessary (i.e. when the docker image inside the operator definition has been updated.)
* checks running clusters against the manifests and acts on the differences found. * periodically checks running clusters against the manifests and acts on the differences found.
For instance, when the user creates a new custom object of type postgresql by submitting a new manifest with kubectl, the operator fetches that object and creates the corresponding kubernetes structures (statefulsets, services, secrets) according to its definition. For instance, when the user creates a new custom object of type postgresql by submitting a new manifest with kubectl, the operator fetches that object and creates the corresponding kubernetes structures (statefulsets, services, secrets) according to its definition.
@ -104,7 +104,7 @@ will get you the docker image built and deployed.
$ make docker $ make docker
$ sed -e "s/\(image\:.*\:\).*$/\1$TAG/" -e "/serviceAccountName/d" manifests/postgres-operator.yaml|kubectl create -f - $ sed -e "s/\(image\:.*\:\).*$/\1$TAG/" -e "/serviceAccountName/d" manifests/postgres-operator.yaml|kubectl create -f -
The last line changes the docker image tag in the maniest to the one the operator image has been built with and removes The last line changes the docker image tag in the manifest to the one the operator image has been built with and removes
the serviceAccountName definition, as the service account is not defined in minikube (neither it should, as one has admin the serviceAccountName definition, as the service account is not defined in minikube (neither it should, as one has admin
permissions there). permissions there).