add 3

charts/postgres-operator/values.yaml

@@ -186,7 +186,7 @@ configKubernetes:
   # namespaced name of the ConfigMap with environment variables to populate on every pod
   # pod_environment_configmap: "default/my-custom-config"
   # name of the Secret (in cluster namespace) with environment variables to populate on every pod
-  # pod_environment_secret: "my-custom-secret"
+  pod_environment_secret: "" # TODO
 
   # specify the pod management policy of stateful sets of Postgres clusters
   pod_management_policy: "ordered_ready"
@@ -194,17 +194,18 @@ configKubernetes:
   pod_role_label: spilo-role
   # service account definition as JSON/YAML string to be used by postgres cluster pods
   # pod_service_account_definition: ""
+  # TODO pod_service_account_definition: '{ "apiVersion": "v1", "kind": "ServiceAccount", "metadata": { "name": "postgres-pod" }, "imagePullSecrets": [ { "name": "registry-secret" } ] }'
 
   # role binding definition as JSON/YAML string to be used by pod service account
   # pod_service_account_role_binding_definition: ""
 
   # Postgres pods are terminated forcefully after this timeout
-  pod_terminate_grace_period: 5m
+  pod_terminate_grace_period: 1m # TODO 5m
   # template for database user secrets generated by the operator,
   # here username contains the namespace in the format namespace.username
   # if the user is in different namespace than cluster and cross namespace secrets
   # are enabled via `enable_cross_namespace_secret` flag in the configuration.
-  secret_name_template: "{username}.{cluster}.credentials.{tprkind}.{tprgroup}"
+  secret_name_template: "{username}.{cluster}" # TODO "{username}.{cluster}.credentials.{tprkind}.{tprgroup}"
   # sharing unix socket of PostgreSQL (`pg_socket`) with the sidecars
   share_pgsocket_with_sidecars: false
   # set user and group for the spilo container (required to run Spilo as non-root process)
@@ -258,7 +259,7 @@ configTimeouts:
   # timeout when waiting for successful response from Patroni API
   patroni_api_check_timeout: 5s
   # timeout when waiting for the Postgres pods to be deleted
-  pod_deletion_wait_timeout: 10m
+  pod_deletion_wait_timeout: 3m # TODO 10m
   # timeout when waiting for pod role and cluster labels
   pod_label_wait_timeout: 10m
   # interval between consecutive attempts waiting for postgresql CRD to be created
@@ -389,7 +390,7 @@ configLogicalBackup:
   # backup schedule in the cron format
   logical_backup_schedule: "30 00 * * *"
   # secret to be used as reference for env variables in cronjob
-  logical_backup_cronjob_environment_secret: ""
+  logical_backup_cronjob_environment_secret: "logibackup-secrets" # TODO
 
 # automate creation of human users with teams API service
 configTeamsApi:
@@ -478,7 +479,7 @@ priorityClassName: ""
 # priority class for database pods
 podPriorityClassName:
   # If create is false with no name set, no podPriorityClassName is specified.
-  # Hence, the pod priorityClass is the one with globalDefault set. 
+  # Hence, the pod priorityClass is the one with globalDefault set.
   # If there is no PriorityClass with globalDefault set, the priority of Pods with no priorityClassName is zero.
   create: true
   # If not set a name is generated using the fullname template and "-pod" suffix