Postgres operator creates and manages PostgreSQL clusters running in Kubernetes
Go to file
Oleksii Kliukin e1ed4b847d
Use code-generation for CRD API and deepcopy methods (#369)
Client-go provides a https://github.com/kubernetes/code-generator package in order to provide the API to work with CRDs similar to the one available for built-in types, i.e. Pods, Statefulsets and so on.

Use this package to generate deepcopy methods (required for CRDs), instead of using an external deepcopy package; we also generate APIs used to manipulate both Postgres and OperatorConfiguration CRDs, as well as informers and listers for the Postgres CRD, instead of using generic informers and CRD REST API; by using generated code we can get rid of some custom and obscure CRD-related code and use a better API.

All generated code resides in /pkg/generated, with an exception of zz_deepcopy.go in apis/acid.zalan.do/v1

Rename postgres-operator-configuration CRD to OperatorConfiguration, since the former broke naming convention in the code-generator.

Moved Postgresql, PostgresqlList, OperatorConfiguration and OperatorConfigurationList and other types used by them into

Change the type of  the Error field in the Postgresql crd to a string, so that client-go could generate a deepcopy for it.

Use generated code to set status of CRD objects as well. Right now this is done with patch, however, Kubernetes 1.11 introduces the /status subresources, allowing us to set the status with
the special updateStatus call in the future. For now, we keep the code that is compatible with earlier versions of Kubernetes.

Rename postgresql.go to database.go and status.go to logs_and_api.go to reflect the purpose of each of those files.

Update client-go dependencies.

Minor reformatting and renaming.
2018-08-15 17:22:25 +02:00
cmd Allow configuring the operator via the YAML manifest. (#326) 2018-07-16 16:20:46 +02:00
docker Fix typo in port (#219) 2018-02-02 15:51:26 +01:00
docs Use code-generation for CRD API and deepcopy methods (#369) 2018-08-15 17:22:25 +02:00
hack Use code-generation for CRD API and deepcopy methods (#369) 2018-08-15 17:22:25 +02:00
manifests Use code-generation for CRD API and deepcopy methods (#369) 2018-08-15 17:22:25 +02:00
pkg Use code-generation for CRD API and deepcopy methods (#369) 2018-08-15 17:22:25 +02:00
.gitignore Initial implementation for the statefulset annotations indicating rolling updates. 2018-05-07 08:07:37 +02:00
.travis.yml Update travis configuration. (#332) 2018-06-27 12:30:24 +02:00
.zappr.yaml Add .zappr configuration 2017-05-12 14:51:56 +02:00
CODEOWNERS [WIP] Draft codeowners, update maintainers (#358) 2018-08-06 08:59:00 +02:00
CONTRIBUTING.md Change the broken reference. 2017-05-12 14:56:22 +02:00
LICENSE Move license to the root folder. 2017-05-12 16:16:07 +02:00
MAINTAINERS [WIP] Draft codeowners, update maintainers (#358) 2018-08-06 08:59:00 +02:00
Makefile Improvements for debug mode 2018-02-02 11:17:12 +01:00
README.md Docs/reference (#323) 2018-06-12 19:12:11 +02:00
SECURITY.md docs(general): Adding Security.md (#88) 2017-09-04 14:33:30 +02:00
build-ci.sh Use zalando incubator instead of an old repo 2017-05-12 14:57:58 +02:00
delivery.yaml Some fixes for travis ci and cdp 2018-03-27 16:05:13 +02:00
glide.lock Use code-generation for CRD API and deepcopy methods (#369) 2018-08-15 17:22:25 +02:00
glide.yaml Use code-generation for CRD API and deepcopy methods (#369) 2018-08-15 17:22:25 +02:00
mkdocs.yml Docs/reference (#323) 2018-06-12 19:12:11 +02:00
run_operator_locally.sh Fix conf for minikube (#301) 2018-05-25 12:25:42 +02:00

README.md

Postgres Operator

Build Status Coverage Status Go Report Card

Introduction

The Postgres operator manages PostgreSQL clusters on Kubernetes:

  1. The operator watches additions, updates, and deletions of PostgreSQL cluster manifests and changes the running clusters accordingly. For example, when a user submits a new manifest, the operator fetches that manifest and spawns a new Postgres cluster along with all necessary entities such as Kubernetes StatefulSets and Postgres roles. See this Postgres cluster manifest for settings that a manifest may contain.

  2. The operator also watches updates to its own configuration and alters running Postgres clusters if necessary. For instance, if a pod docker image is changed, the operator carries out the rolling update. That is, the operator re-spawns one-by-one pods of each StatefulSet it manages with the new Docker image.

  3. Finally, the operator periodically synchronizes the actual state of each Postgres cluster with the desired state defined in the cluster's manifest.

There is a browser-friendly version of this documentation at postgres-operator.readthedocs.io

Table of contents

the rest of the document is a tutorial to get you up and running with the operator on Minikube.

Quickstart

Prerequisites:

Note that you can also use built-in Kubernetes support in the Docker Desktop for Mac to follow the steps of this tutorial. You would have to replace minikube start and minikube delete with your launch actionsfor the Docker built-in Kubernetes support.

Local execution

git clone https://github.com/zalando-incubator/postgres-operator.git
cd postgres-operator

minikube start

# start the operator; may take a few seconds
kubectl create -f manifests/configmap.yaml  # configuration
kubectl create -f manifests/operator-service-account-rbac.yaml  # identity and permissions
kubectl create -f manifests/postgres-operator.yaml  # deployment

# create a Postgres cluster
kubectl create -f manifests/minimal-postgres-manifest.yaml

# connect to the Postgres master via psql
# operator creates the relevant k8s secret
export HOST_PORT=$(minikube service acid-minimal-cluster --url | sed 's,.*/,,')
export PGHOST=$(echo $HOST_PORT | cut -d: -f 1)
export PGPORT=$(echo $HOST_PORT | cut -d: -f 2)
export PGPASSWORD=$(kubectl get secret postgres.acid-minimal-cluster.credentials -o 'jsonpath={.data.password}' | base64 -d)
psql -U postgres

# tear down cleanly
minikube delete

We have automated starting the operator and submitting the acid-minimal-cluster for you:

cd postgres-operator
./run_operator_locally.sh

Running and testing the operator

The best way to test the operator is to run it in minikube. Minikube is a tool to run Kubernetes cluster locally.

Configuration Options

The operator can be configured with the provided ConfigMap (manifests/configmap.yaml).