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.asciidoc
+7-3Lines changed: 7 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -5,20 +5,24 @@ v1.0.0, {docdate}
5
5
6
6
The PostgreSQL Operator provides a Kubernetes operator capability for managing PostgreSQL Databases and Clusters deployed within a Kubernetes.
7
7
8
-
The PostgreSQL Operator leverages a Kubernetes Third Party Resources in order to define custom Kubernetes objects such as 'Database Name'and 'Cluster Name'.
8
+
The PostgreSQL Operator leverages Kubernetes Third Party Resources to define custom resource types *pgdatabase*and *pgcluster*.
9
9
10
10
Once those custom objects are defined, Kubernetes provides the ability to create and manage those objects similar to any other native Kubernetes object.
11
11
12
-
The PostgreSQL Operator runs within Kubernetes enabling Kubernetes to detect these new custom object types being created or removed.
12
+
The PostgreSQL Operator runs within Kubernetes detecting these new custom object types being created or removed.
13
13
14
-
Once the objects are detected, the PostgreSQL Operator enables useres to perform operations across the Kubernetes environment, including
14
+
Once the objects are detected, the PostgreSQL Operator enables users to perform operations across the Kubernetes environment, including:
15
15
16
16
* Create Database or Cluster
17
17
* Destroy Database or Cluster
18
18
* Backup Database or Cluster
19
19
* Restore Database or Cluster
20
20
* View PVC
21
21
22
+
What actually gets created on the Kube cluster for a *pgdatabase* or
23
+
*pgcluster* resource is defined as a *deployment strategy*. Strategies
24
+
are documented in detail here link:docs/strategies.asciidoc[Deployment Strategies]
0 commit comments