|
53 | 53 |
|
54 | 54 | ## Watch pods being created |
55 | 55 |
|
| 56 | +Check if the database pods are coming up. Use the label `application=spilo` to |
| 57 | +filter and list the label `spilo-role` to see when the master is promoted and |
| 58 | +replicas get their labels. |
| 59 | + |
| 60 | +```bash |
| 61 | +kubectl get pods -l application=spilo -L spilo-role -w |
| 62 | +``` |
| 63 | + |
| 64 | +The operator also emits K8s events to the Postgresql CRD which can be inspected |
| 65 | +in the operator logs or with: |
| 66 | + |
56 | 67 | ```bash |
57 | | -kubectl get pods -w --show-labels |
| 68 | +kubectl describe postgresql acid-minimal-cluster |
58 | 69 | ``` |
59 | 70 |
|
60 | 71 | ## Connect to PostgreSQL |
@@ -736,14 +747,14 @@ spin up more instances). |
736 | 747 |
|
737 | 748 | ## Custom TLS certificates |
738 | 749 |
|
739 | | -By default, the spilo image generates its own TLS certificate during startup. |
| 750 | +By default, the Spilo image generates its own TLS certificate during startup. |
740 | 751 | However, this certificate cannot be verified and thus doesn't protect from |
741 | 752 | active MITM attacks. In this section we show how to specify a custom TLS |
742 | 753 | certificate which is mounted in the database pods via a K8s Secret. |
743 | 754 |
|
744 | 755 | Before applying these changes, in k8s the operator must also be configured with |
745 | 756 | the `spilo_fsgroup` set to the GID matching the postgres user group. If you |
746 | | -don't know the value, use `103` which is the GID from the default spilo image |
| 757 | +don't know the value, use `103` which is the GID from the default Spilo image |
747 | 758 | (`spilo_fsgroup=103` in the cluster request spec). |
748 | 759 |
|
749 | 760 | OpenShift allocates the users and groups dynamically (based on scc), and their |
@@ -805,5 +816,5 @@ spec: |
805 | 816 | Alternatively, it is also possible to use |
806 | 817 | [cert-manager](https://cert-manager.io/docs/) to generate these secrets. |
807 | 818 |
|
808 | | -Certificate rotation is handled in the spilo image which checks every 5 |
| 819 | +Certificate rotation is handled in the Spilo image which checks every 5 |
809 | 820 | minutes if the certificates have changed and reloads postgres accordingly. |
0 commit comments