delete unused files, edit Readme and create manifest Readme

Author: Yannic Nevado Hidalgo

Readme.md

@@ -1,6 +1,6 @@
 # Custom Postgres Operator
 
-This repository contains a custom setup for an [HA](https://www.postgresql.org/docs/current/high-availability.html) [Postgres](https://www.postgresql.org/) cluster, based on [Postgres Operator](https://github.com/zalando/postgres-operator) from [Patroni](https://github.com/zalando/spilo).
+This repository contains a custom setup for an [HA](https://www.postgresql.org/docs/current/high-availability.html) [Postgres](https://www.postgresql.org/) cluster, based on [Postgres Operator](https://github.com/zalando/postgres-operator) from [Patroni](https://github.com/zalando/spilo). The manifest folder only contains the minimum needed YAML files for the setup.
 
 The Cluster runs on an [K8s](https://kubernetes.io/) Cluster which is managed by [Rancher](https://rancher.com/) and hosted at the infrastructure of Proventa AG.
 
@@ -16,7 +16,7 @@ The Cluster runs on an [K8s](https://kubernetes.io/) Cluster which is managed by
 
 ## Installation
 
-The installation will be executed by applying manifests in a specific order, based on the operator installation from patroni. The setup is deployed to an specific namespace  named *zalando-postgres* which must be ceated on the K8s cluster. You also can setup the operator(+Postgres cluster) with Helm chart or Operator Lifecycle Manager.
+The installation will be executed by applying manifests in a specific order, based on the operator installation from Patroni. The setup is deployed to an specific namespace  named *zalando-postgres*, which must be ceated first on the K8s cluster. You also can setup the operator(+Postgres cluster) with Helm chart or Operator Lifecycle Manager.
 (fyi: you can also set the current-context for kubectl, here ns=zalando-postgres for example)
 
 ### Create the operator

manifests/Readme.md

@@ -1 +1,48 @@
-# Manifest Files
+# Manifest Files
+
+## `complete-postgres-manifest.yaml`
+
+* near all Postgres cluster configuration options for deploying Postgres cluster
+  *  Dockerimage: [Spilo](https://github.com/zalando/spilo)
+  * replicas
+  * users
+  * Container resources
+  * postgresql.conf parameters
+  * pg_hba.conf
+  * logical backups to s3 (required Docker Image)
+
+
+## `minimal-postgres-manifest.yaml`
+
+* configured file for specific setup of Postgres cluster
+* same as above with minimal options set
+
+
+## `configmap.yaml`
+
+* configuration options for the Postgres operator
+
+
+## `operator-service-account-rbac.yaml`
+
+* definied ClusterRole, ClusterRoleBinding and ServiceAccount for Postgres operator
+
+
+## `postgres-operator.yaml`
+
+* definition of Postgres operator with template and reference to created ConfigMap
+
+
+## `postgresql-operator-default-configuration.yaml`
+
+* near all configuration options for the Postgres operator
+
+
+## `standby-manifest.yaml`
+
+* create a standby cluster from an s3 backup
+
+
+## `user-facing-clusterroles.yaml`
+
+* defining ClusterRoles for Postgrs operator