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

fixing typos in postgres-sql #460

Merged
merged 1 commit into from
Feb 6, 2024
Merged

fixing typos in postgres-sql #460

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
4 changes: 2 additions & 2 deletions src/reference-designs/postgres-sql.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ High Availability (HA) failover in PostgreSQL supported by Tanzu-powered backend
The following components have been utilized for the deployment of PostgreSQL High Availability (HA) failover system:

### Tanzu Infrastructure Integration
We leveraged Tanzu Kubernetes Grid (informally known as TKGm) 2.3.0 to create a well-configured and highly available infrastructure for our PostgreSQL deployment. The Tanzu Infrastructure played a important role in optimizing the deployment and management of PostgreSQL, adding further value to the failover capabilities.
We leveraged Tanzu Kubernetes Grid (informally known as TKGm) 2.3.0 to create a well-configured and highly available infrastructure for our PostgreSQL deployment. The Tanzu Infrastructure played an important role in optimizing the deployment and management of PostgreSQL, adding further value to the failover capabilities.


### Centralized Management with Tanzu
Expand Down Expand Up @@ -158,7 +158,7 @@ The following component versions and interoperability matrix are supported with
> **Note** Update the `pg_hba.conf` file to allow necessary host connections for replication, ensuring secure communication between the nodes.

1. Initiate Failover. <br>
To initiate the failover, the primary node is gracefully scaled down to zero replicas, allowing the standby node in different namespace to take over seamlessly so that we can verify it by checking the `kubectl` logs
To initiate the failover, the primary node is gracefully scaled down to zero replicas, allowing the standby node in a different namespace to take over seamlessly so that we can verify it by checking the `kubectl` logs

```bash
# kubectl scale sts/primary-repmgr-postgresql-ha-postgresql --replicas=0 -n primary
Expand Down
Loading