make run.sh executable from within e2e (#619)

This commit is contained in:
Felix Kunde
2019-07-24 15:07:32 +02:00
committed by GitHub
parent 1d45a6aec3
commit cd350a4bc1
20 changed files with 169 additions and 61 deletions
+1 -1
View File
@@ -135,7 +135,7 @@ These parameters are grouped directly under the `spec` key in the manifest.
to S3. Default: false. Optional.
* **logicalBackupSchedule**
Schedule for the logical backup k8s cron job. Please take
Schedule for the logical backup K8s cron job. Please take
[the reference schedule format](https://kubernetes.io/docs/tasks/job/automated-tasks-with-cron-jobs/#schedule)
into account. Optional. Default is: "30 00 \* \* \*"
+3 -3
View File
@@ -158,8 +158,8 @@ configuration they are grouped under the `kubernetes` key.
* **pod_service_account_role_binding_definition**
This definition must bind pod service account to a role with permission
sufficient for the pods to start and for Patroni to access k8s endpoints;
service account on its own lacks any such rights starting with k8s v1.8. If
sufficient for the pods to start and for Patroni to access K8s endpoints;
service account on its own lacks any such rights starting with K8s v1.8. If
not explicitly defined by the user, a simple definition that binds the
account to the operator's own 'zalando-postgres-operator' cluster role will
be used. The default is empty.
@@ -416,7 +416,7 @@ yet officially supported.
## Logical backup
These parameters configure a k8s cron job managed by the operator to produce
These parameters configure a K8s cron job managed by the operator to produce
Postgres logical backups. In the CRD-based configuration those parameters are
grouped under the `logical_backup` key.