@@ -22,6 +22,17 @@ Next deploy the postgres-operator from the docker image Zalando is using:
22
22
23
23
If you prefer to build the image yourself follow up down below.
24
24
25
+ ### - Helm chart
26
+
27
+ You can install postgres-operator with also with a [ Helm] ( https://helm.sh/ )
28
+ chart. This requires installing the Helm CLI, first and then initializing it
29
+ in the cluster.
30
+
31
+ ``` bash
32
+ $ helm init
33
+ $ helm install --name my-release ./charts/postgres-operator
34
+ ```
35
+
25
36
## Check if CustomResourceDefinition has been registered
26
37
27
38
``` bash
@@ -312,7 +323,7 @@ generated from the current cluster manifest. There are two types of scans:
312
323
* `sync scan`, running every `resync_period` seconds for every cluster
313
324
314
325
* `repair scan`, coming every `repair_period` only for those clusters that didn't
315
- report success as a result of the last operation applied to them.
326
+ report success as a result of the last operation applied to them.
316
327
317
328
# # Postgres roles supported by the operator
318
329
@@ -329,8 +340,8 @@ Postgres database cluster:
329
340
330
341
# # Understanding rolling update of Spilo pods
331
342
332
- The operator logs reasons for a rolling update with the `info` level and
333
- a diff between the old and new StatefulSet specs with the `debug` level.
343
+ The operator logs reasons for a rolling update with the `info` level and
344
+ a diff between the old and new StatefulSet specs with the `debug` level.
334
345
To read the latter log entry with the escaped characters rendered, view it
335
346
in CLI with `echo -e`. Note that the resultant message will contain some
336
347
noise because the `PodTemplate` used by the operator is yet to be updated
0 commit comments