finally working setup after upgrading rancher, rancheros and kubernetesgit add .

Author: Yannic Nevado Hidalgo

Readme.md

@@ -26,38 +26,38 @@ The installation will be executed by applying manifests in a specific order, bas
 
 ```shell
 # operator configuration
-$ kubectl create -f manifests/configmap.yaml --namespace zalando-postgres
+kubectl create -f manifests/configmap.yaml --namespace zalando-postgres
 # identity and permissions
-$ kubectl create -f manifests/operator-service-account-rbac.yaml --namespace zalando-postgres
+kubectl create -f manifests/operator-service-account-rbac.yaml --namespace zalando-postgres
 # deploy operator to K8s
-$ kubectl create -f manifests/postgres-operator.yaml --namespace zalando-postgres
+kubectl create -f manifests/postgres-operator.yaml --namespace zalando-postgres
 ```
 
 ### Check operator status
 
 * get all pods in the `namespace zalando-postgres` with the operator label `name=postgres-operator`
 
 ```shell
-$ kubectl get pod -l name=postgres-operator --namespace zalando-postgres
+kubectl get pod -l name=postgres-operator --namespace zalando-postgres
 ```
 
 ### Create Postgres cluster
 
 * create a Postgres cluster from [postgres manifest](https://github.com/yanehi/custom-postgres-operator/blob/master/manifests/minimal-postgres-manifest.yaml) with the specified values, like databases, users and *postgresql.conf* parameters
 
 ```shell
-$ kubectl create -f manifests/minimal-postgres-manifest.yaml --namespace zalando-postgres
+kubectl create -f manifests/minimal-postgres-manifest.yaml --namespace zalando-postgres
 ```
 
 ### Check Postgres cluster status
 
 ```shell
 # check the deployed cluster
-$ kubectl get postgresql
+kubectl get postgresql
 # check created database pods with spilo-role (master, replica)
-$ kubectl get pods -l application=spilo -L spilo-role --namespace zalando-postgres
+kubectl get pods -l application=spilo -L spilo-role --namespace zalando-postgres
 # check created service resources and get ext. loadbalancer ip and port
-$ kubectl get svc -l application=spilo -L spilo-role --namespace zalando-postgres
+kubectl get svc -l application=spilo -L spilo-role --namespace zalando-postgres
 ```
 
 ### Update Pod Manifest
@@ -74,13 +74,13 @@ You can update the Postgres cluster with the *manifest file* or directly with *p
 * required `pg_hba.conf` entry for the external LoadBalancer IP
 
 ```shell
-$ psql -h <LoadBalancer-IP> -p <LoadBalancer-Port>  -d <databasename> -U <databaseuser>
+psql -h <LoadBalancer-IP> -p <LoadBalancer-Port>  -d <databasename> -U <databaseuser>
 ```
 
 * connect directly from shell in Rancher
 
 ```shell
-$ psql -d <databasename> -U <databaseuser>
+psql -d <databasename> -U <databaseuser>
 ```
 
 ### Delete Postgres Cluster

manifests/minimal-postgres-manifest.yaml

@@ -19,7 +19,7 @@ spec:
     storageClass: standard
   # number of pods
   # 1 is master, others replicas
-  numberOfInstances: 2
+  numberOfInstances: 3
   # define some users with access rights
   users:
     zalando:  # database owner

manifests/postgres-operator.yaml

@@ -21,7 +21,7 @@ spec:
       # every postgres-operator Deployment Pod contains one container
       containers:
       - name: postgres-operator
-        image: registry.opensource.zalan.do/acid/postgres-operator:v1.2.0
+        image: registry.opensource.zalan.do/acid/postgres-operator:latest
         imagePullPolicy: IfNotPresent
         # set requested and limited resources for the container
         resources:

reset_postgres_operator_setup.sh

@@ -14,4 +14,6 @@ kubectl delete configmaps postgres-operator -n zalando-postgres
 
 kubectl delete postgresql acid-minimal-cluster --namespace zalando-postgres
 
-kubectl delete service acid-minimal-cluster acid-minimal-cluster-repl -n zalando-postgres
+kubectl delete service acid-minimal-cluster acid-minimal-cluster-repl -n zalando-postgres
+
+kubectl delete poddisruptionbudgets postgres-acid-minimal-cluster-pdb -n zalando-postgres