Skip to content

Commit

Permalink
persistence/postgres: tier is now required in minimal config
Browse files Browse the repository at this point in the history
  • Loading branch information
FredrikMeyer authored Aug 22, 2024
1 parent 8fd632d commit 6ccc79b
Showing 1 changed file with 2 additions and 1 deletion.
3 changes: 2 additions & 1 deletion docs/persistence/postgres/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -32,13 +32,14 @@ spec:
gcp:
sqlInstances:
- type: POSTGRES_14
tier: db-f1-micro
databases:
- name: mydb
```
!!! important "Choosing the right tier for production"
By default, the database server is `db-f1-micro` which has 1 vCPU, 614 MB RAM and 10GB of SSD storage with no automatic storage increase. Shared CPU machine types (`db-f1-micro` and `db-g1-small`) are **NOT** covered by the [Cloud SQL SLA](https://cloud.google.com/sql/sla). Consider [changing](../../workloads/application/reference/application-spec.md#gcpsqlinstancestier) to the `db-custom-CPU-RAM` tier for your production databases. Please also note that exhausting disk and/or CPU with automatic increase disabled is [not](https://cloud.google.com/sql/docs/postgres/operational-guidelines) covered by the SLA.
The database in the minimal configuration, `db-f1-micro`, has 1 vCPU, 614 MB RAM and 10GB of SSD storage with no automatic storage increase. Shared CPU machine types (`db-f1-micro` and `db-g1-small`) are **NOT** covered by the [Cloud SQL SLA](https://cloud.google.com/sql/sla). Consider [changing](../../workloads/application/reference/application-spec.md#gcpsqlinstancestier) to the `db-custom-CPU-RAM` tier for your production databases. Please also note that exhausting disk and/or CPU with automatic increase disabled is [not](https://cloud.google.com/sql/docs/postgres/operational-guidelines) covered by the SLA.

## Example with all configuration options

Expand Down

0 comments on commit 6ccc79b

Please sign in to comment.