Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

CLOUD-838 - Fix dataVolumeClaimSpec...storage in README #252

Merged
merged 5 commits into from
Feb 1, 2024
Merged

CLOUD-838 - Fix dataVolumeClaimSpec...storage in README #252

Changes from 2 commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
14d9241
Fix dataVolumeClaimSpec storage in README
mrrsm Oct 12, 2023
87a17f0
Merge branch 'main' into hotfix/pg-db-values-docs
egegunes Jan 19, 2024
1d5b0c9
Bump pg-db chart version
mrrsm Jan 23, 2024
7b00398
Merge branch 'main' into hotfix/pg-db-values-docs
tplavcic Feb 1, 2024
094a502
Minor fix in pg-db README.md
tplavcic Feb 1, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions charts/pg-db/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,7 +39,7 @@ The chart can be customized using the following configurable parameters:
| `port` | PostgreSQL port | `5432` |
| `postgresVersion` | PostgreSQL container version tag | `16` |
| `pause` | Stop PostgreSQL Database safely | `false` |
| `unmanaged` | Start cluster and don't manage it (cross cluster replication) | `false`
| `unmanaged` | Start cluster and don't manage it (cross cluster replication) | `false`
| `standby.enabled` | Switch/start PostgreSQL Database in standby mode | `false` |
| `standby.host` | Host address of the primary cluster this standby cluster connects to | `` |
| `standby.port` | Port number used by a standby copy to connect to the primary cluster | `` |
Expand Down Expand Up @@ -87,7 +87,7 @@ The chart can be customized using the following configurable parameters:
| `instances.walVolumeClaimSpec.accessModes` | The Kubernetes PersistentVolumeClaim access modes for the PostgreSQL Write-ahead Log storage | `ReadWriteOnce` |
| `instances.walVolumeClaimSpec.resources.requests.storage` | The Kubernetes storage requests for the storage the PostgreSQL instance will use | `1Gi` |
| `instances.dataVolumeClaimSpec.accessModes` | The Kubernetes PersistentVolumeClaim access modes for the PostgreSQL Write-ahead Log storage | `ReadWriteOnce` |
| `instances.walVolumeClaimSpec.resources.requests.storage` | The Kubernetes storage requests for the storage the PostgreSQL instance will use | `1Gi` |
| `instances.dataVolumeClaimSpec.resources.requests.storage` | The Kubernetes storage requests for the storage the PostgreSQL instance will use | `1Gi` |
| `backups.pgbackrest.metadata.labels` | Set labels for pgbackrest | `test-label:test` |
| `backups.pgbackrest.configuration.secret.name` | Name of the Kubernetes Secret object with custom pgBackRest configuration, which will be added to the pgBackRest configuration generated by the Operator | `cluster1-pgbackrest-secrets` |
| `backups.pgbackrest.jobs.priorityClassName` | The Kuberentes Pod priority class for pgBackRest jobs | `high-priority` |
Expand Down Expand Up @@ -135,7 +135,7 @@ The chart can be customized using the following configurable parameters:
| `proxy.pgBouncer.tolerations.effect` | The Kubernetes Pod tolerations effect for the PostgreSQL instance | `NoSchedule` |
| `proxy.pgBouncer.tolerations.key` | The Kubernetes Pod tolerations key for the PostgreSQL instance | `role` |
| `proxy.pgBouncer.tolerations.operator` | The Kubernetes Pod tolerations operator for the PostgreSQL instance | `Equal` |
| `proxy.pgBouncer.tolerations.value` | The Kubernetes Pod tolerations value for the PostgreSQL instance
| `proxy.pgBouncer.tolerations.value` | The Kubernetes Pod tolerations value for the PostgreSQL instance
| `proxy.pgBouncer.customTLSSecret.name` | Custom external TLS secret name | `keycloakdb-pgbouncer.tls` |
| `proxy.pgBouncer.affinity.podAntiAffinity` | Pod anti-affinity, allows setting the standard Kubernetes affinity constraints of any complexity | `{}` |
| `proxy.pgBouncer.image` | Set this variable if you need to use a custom pgbouncer image | `percona/percona-postresql-operator:1.4.0-ppg14-pgbouncer` |
Expand Down Expand Up @@ -172,7 +172,7 @@ Notice that you can use multiple replica sets only with sharding enabled.

### Deploy for tests - single PostgreSQL node and automated PVCs deletion

Such a setup is good for testing, as it does not require a lot of compute power
Such a setup is good for testing, as it does not require a lot of compute power
and performs and automated clean up of the Persistent Volume Claims (PVCs).
It also deploys just one pgBouncer node, instead of 3.
```bash
Expand All @@ -190,7 +190,7 @@ Expose the cluster's pgBouncer with a LoadBalancer:

```bash
$ helm install my-test percona/pg-db \
--set proxy.pgBouncer.expose.type=LoadBalancer
--set proxy.pgBouncer.expose.type=LoadBalancer
```

### Add a custom user and a database
Expand Down
Loading