You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+12-12Lines changed: 12 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,19 +6,19 @@
6
6
7
7
# Run your own production-grade PostgreSQL-as-a-Service on Kubernetes!
8
8
9
-
The Crunchy PostgreSQL Operator automates and simplifies deploying and managing open source PostgreSQL clusters on Kubernetes and other Kubernetes-enabled Platforms by providing the essential features you need to keep your PostgreSQL clusters up and running, including:
9
+
The [Crunchy PostgreSQL Operator](https://access.crunchydata.com/documentation/postgres-operator/) automates and simplifies deploying and managing open source PostgreSQL clusters on Kubernetes and other Kubernetes-enabled Platforms by providing the essential features you need to keep your PostgreSQL clusters up and running, including:
10
10
11
11
#### PostgreSQL Cluster Provisioning
12
12
13
-
Create, Scale, & Delete PostgreSQL clusters with ease, while fully customizing your Pods and PostgreSQL configuration!
13
+
[Create, Scale, & Delete PostgreSQL clusters with ease](https://access.crunchydata.com/documentation/postgres-operator/latest/architecture/provisioning/), while fully customizing your Pods and PostgreSQL configuration!
14
14
15
15
#### High-Availability
16
16
17
-
Safe, automated failover backed by a distributed consensus based HA solution. Uses [Pod Anti-Affinity](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#inter-pod-affinity-and-anti-affinity) to help resiliency; you can configure how aggressive this can be! Failed primaries automatically heal, allowing for faster recovery time.
17
+
Safe, automated failover backed by a [distributed consensus based high-availability solution](https://access.crunchydata.com/documentation/postgres-operator/latest/architecture/high-availability/). Uses [Pod Anti-Affinity](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#inter-pod-affinity-and-anti-affinity) to help resiliency; you can configure how aggressive this can be! Failed primaries automatically heal, allowing for faster recovery time.
18
18
19
19
#### Disaster Recovery
20
20
21
-
Backups and restores leverage the open source [pgBackRest](https://www.pgbackrest.org) utility and includes support for full, incremental, and differential backups as well as efficient delta restores. Set how long you want your backups retained for. Works great with very large databases!
21
+
Backups and restores leverage the open source [pgBackRest](https://www.pgbackrest.org) utility and [includes support for full, incremental, and differential backups as well as efficient delta restores](https://access.crunchydata.com/documentation/postgres-operator/latest/architecture/disaster-recovery/). Set how long you want your backups retained for. Works great with very large databases!
22
22
23
23
#### Monitoring
24
24
@@ -34,27 +34,27 @@ Safely apply PostgreSQL updates with minimal availability impact to your Postgre
34
34
35
35
#### Advanced Replication Support
36
36
37
-
Choose between asynchronous replication and, for workloads that are sensitive to losing transactions, synchronous replication
37
+
Choose between [asynchronous replication](https://access.crunchydata.com/documentation/postgres-operator/latest/architecture/high-availability/) and[synchronous replication](https://access.crunchydata.com/documentation/postgres-operator/latest/architecture/high-availability/#synchronous-replication-guarding-against-transactions-loss)for workloads that are sensitive to losing transactions.
38
38
39
39
#### Clone
40
40
41
-
Create new clusters from your existing clusters with a simple `pgo clone` command.
41
+
Create new clusters from your existing clusters with a simple [`pgo clone`](https://access.crunchydata.com/documentation/postgres-operator/latest/pgo-client/reference/pgo_clone/) command.
42
42
43
43
#### Connection Pooling
44
44
45
-
Use [pgBouncer](https://access.crunchydata.com/documentation/pgbouncer/) for connection pooling
45
+
Use [pgBouncer](https://access.crunchydata.com/documentation/pgbouncer/) for connection pooling
46
46
47
47
#### Node Affinity
48
48
49
49
Have your PostgreSQL clusters deployed to [Kubernetes Nodes](https://kubernetes.io/docs/concepts/architecture/nodes/) of your preference
50
50
51
51
#### Scheduled Backups
52
52
53
-
Choose the type of backup (full, incremental, differential) and how frequently you want it to occur on each PostgreSQL cluster.
53
+
Choose the type of backup (full, incremental, differential) and [how frequently you want it to occur](https://access.crunchydata.com/documentation/postgres-operator/latest/architecture/disaster-recovery/#scheduling-backups) on each PostgreSQL cluster.
54
54
55
55
#### Backup to S3
56
56
57
-
Store your backups in Amazon S3 or any object storage system that supports the S3 protocol. The PostgreSQL Operator can backup, restore, and create new clusters from these backups.
57
+
[Store your backups in Amazon S3](https://access.crunchydata.com/documentation/postgres-operator/latest/architecture/disaster-recovery/#using-s3) or any object storage system that supports the S3 protocol. The PostgreSQL Operator can backup, restore, and create new clusters from these backups.
58
58
59
59
#### Multi-Namespace Support
60
60
@@ -139,16 +139,16 @@ For a quick start deployment to Google Kubernetes Engine (GKE), please see instr
139
139
140
140
If you have the PostgreSQL Operator installed in your environment, and are interested in installation of the client interface, please start here:
There is also a `pgo-client` container if you wish to deploy the client directly to your Kubernetes environment.
145
145
146
146
### Using the PostgreSQL Operator
147
147
148
148
If you have the PostgreSQL and Client Interface installed in your environment and are interested in guidance on the use of the Crunchy PostgreSQL Operator, please start here:
Copy file name to clipboardExpand all lines: hugo/content/_index.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,15 +16,15 @@ The Crunchy PostgreSQL Operator automates and simplifies deploying and managing
16
16
17
17
#### PostgreSQL Cluster Provisioning
18
18
19
-
Create, Scale, & Delete PostgreSQL clusters with ease, while fully customizing your Pods and PostgreSQL configuration!
19
+
[Create, Scale, & Delete PostgreSQL clusters with ease](/architecture/provisioning/), while fully customizing your Pods and PostgreSQL configuration!
20
20
21
21
#### High-Availability
22
22
23
-
Safe, automated failover backed by a distributed consensus based HA solution. Uses [Pod Anti-Affinity](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#inter-pod-affinity-and-anti-affinity) to help resiliency; you can configure how aggressive this can be! Failed primaries automatically heal, allowing for faster recovery time.
23
+
Safe, automated failover backed by a [distributed consensus based high-availability solution](/architecture/high-availability/). Uses [Pod Anti-Affinity](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#inter-pod-affinity-and-anti-affinity) to help resiliency; you can configure how aggressive this can be! Failed primaries automatically heal, allowing for faster recovery time.
24
24
25
25
#### Disaster Recovery
26
26
27
-
Backups and restores leverage the open source [pgBackRest](https://www.pgbackrest.org) utility and includes support for full, incremental, and differential backups as well as efficient delta restores. Set how long you want your backups retained for. Works great with very large databases!
27
+
Backups and restores leverage the open source [pgBackRest](https://www.pgbackrest.org) utility and [includes support for full, incremental, and differential backups as well as efficient delta restores](/architecture/disaster-recovery/). Set how long you want your backups retained for. Works great with very large databases!
28
28
29
29
#### Monitoring
30
30
@@ -40,11 +40,11 @@ Safely apply PostgreSQL updates with minimal availability impact to your Postgre
40
40
41
41
#### Advanced Replication Support
42
42
43
-
Choose between asynchronous replication and, for workloads that are sensitive to losing transactions, synchronous replication
43
+
Choose between [asynchronous replication](/architecture/high-availability/) and[synchronous replication](/architecture/high-availability/#synchronous-replication-guarding-against-transactions-loss)for workloads that are sensitive to losing transactions.
44
44
45
45
#### Clone
46
46
47
-
Create new clusters from your existing clusters with a simple `pgo clone` command.
47
+
Create new clusters from your existing clusters with a simple [`pgo clone`](/pgo-client/reference/pgo_clone/) command.
48
48
49
49
#### Connection Pooling
50
50
@@ -56,11 +56,11 @@ Have your PostgreSQL clusters deployed to [Kubernetes Nodes](https://kubernetes.
56
56
57
57
#### Scheduled Backups
58
58
59
-
Choose the type of backup (full, incremental, differential) and how frequently you want it to occur on each PostgreSQL cluster.
59
+
Choose the type of backup (full, incremental, differential) and [how frequently you want it to occur](/architecture/disaster-recovery/#scheduling-backups) on each PostgreSQL cluster.
60
60
61
61
#### Backup to S3
62
62
63
-
Store your backups in Amazon S3 or any object storage system that supports the S3 protocol. The PostgreSQL Operator can backup, restore, and create new clusters from these backups.
63
+
[Store your backups in Amazon S3](/architecture/disaster-recovery/#using-s3) or any object storage system that supports the S3 protocol. The PostgreSQL Operator can backup, restore, and create new clusters from these backups.
0 commit comments