Update Patroni Postgres settings for HA environments
What does this MR do?
The MR updates patroni['postgresql']['max_replication_slots'] and patroni['postgresql']['max_wal_senders'] to 6 and 7 accordingly as by design all reference architectures have 3 PG nodes (3 PG instances (x2) / 3 PG instances (x2) + 1). As discussed in https://gitlab.com/gitlab-org/quality/gitlab-environment-toolkit/-/issues/143#note_636904107, the previous numbers were including a Geo instance in HA env setups and should be updated.
Related issues
- Follow-up on !63580 (merged)
- https://gitlab.com/gitlab-org/quality/gitlab-environment-toolkit/-/issues/143#note_636904107
Author's checklist
- Follow the Documentation Guidelines and Style Guide.
- Ensure that the product tier badge is added to doc's
h1. - Request a review based on the documentation page's metadata and associated Technical Writer.
To avoid having this MR be added to code verification QA issues, don't add these labels: feature, frontend, backend, bug, or database
Review checklist
Documentation-related MRs should be reviewed by a Technical Writer for a non-blocking review, based on Documentation Guidelines and the Style Guide.
- If the content requires it, ensure the information is reviewed by a subject matter expert.
- Technical writer review items:
- Ensure docs metadata is present and up-to-date.
- Ensure the appropriate labels are added to this MR.
- If relevant to this MR, ensure content topic type principles are in use, including:
- The headings should be something you'd do a Google search for. Instead of
Default behavior, say something likeDefault behavior when you close an issue. - The headings (other than the page title) should be active. Instead of
Configuring GDK, say something likeConfigure GDK. - Any task steps should be written as a numbered list.
- If the content still needs to be edited for topic types, you can create a follow-up issue with the docs-technical-debt label.
- The headings should be something you'd do a Google search for. Instead of
- Review by assigned maintainer, who can always request/require the above reviews. Maintainer's review can occur before or after a technical writer review.
- Ensure a release milestone is set.
Edited by Nailia Iskhakova