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: docs/content/_index.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ draft: false
6
6
7
7
# PGO: The Postgres Operator from Crunchy Data
8
8
9
-
<imgwidth="25%"src="crunchy_logo.png"/>
9
+
<imgwidth="25%"src="pgo.svg"alt="PGO: The Postgres Operator from Crunchy Data"/>
10
10
11
11
## Run [Cloud Native PostgreSQL on Kubernetes](https://www.crunchydata.com/products/crunchy-postgresql-for-kubernetes/) with PGO: The [Postgres Operator](https://github.com/CrunchyData/postgres-operator) from [Crunchy Data](https://www.crunchydata.com/)!
Copy file name to clipboardExpand all lines: docs/content/installation/_index.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,10 +5,10 @@ draft: false
5
5
weight: 40
6
6
---
7
7
8
-
There are several different ways to install and deploy the [PostgreSQL Operator](https://www.crunchydata.com/developers/download-postgres/containers/postgres-operator)
8
+
There are several different ways to install and deploy the [PGO, the Postgres Operator](https://www.crunchydata.com/developers/download-postgres/containers/postgres-operator)
9
9
based upon your use case.
10
10
11
-
For the vast majority of use cases, we recommend using the [PostgreSQL Operator Installer]({{< relref "/installation/postgres-operator.md" >}}),
11
+
For the vast majority of use cases, we recommend using the [Postgres Operator Installer]({{< relref "/installation/postgres-operator.md" >}}),
12
12
which uses the `pgo-deployer` container to set up all of the objects required to
Copy file name to clipboardExpand all lines: docs/content/installation/metrics/other/ansible/_index.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,17 +5,17 @@ draft: false
5
5
weight: 10
6
6
---
7
7
8
-
# Crunchy Data PostgreSQL Operator Monitoring Playbooks
8
+
# PGO: Postgres Operator Monitoring Playbooks
9
9
10
-
The Crunchy Data PostgreSQL Operator Monitoring Playbooks contain [Ansible](https://www.ansible.com/)
10
+
PGO, the Postgres Operator from Crunchy Data, Monitoring Playbooks contain [Ansible](https://www.ansible.com/)
11
11
roles for installing and managing the [Crunchy Data PostgreSQL Operator Monitoring infrastructure]({{< relref "/installation/other/ansible/installing-operator.md" >}}).
12
12
13
13
## Features
14
14
15
15
The playbooks provided allow users to:
16
16
17
-
* install PostgreSQL Operator Monitoring on Kubernetes and OpenShift
18
-
* install PostgreSQL Operator from a Linux, Mac or Windows (Ubuntu subsystem) host
17
+
* install PGO Monitoring on Kubernetes and OpenShift
18
+
* install PGO from a Linux, Mac or Windows (Ubuntu subsystem) host
## Step 3: Install the PostgreSQL Operator User Keys
46
+
## Step 3: Install the PGO User Keys
48
47
49
48
You will need to get TLS keys used to secure the Operator REST API. Again, in the `pgo` namespace:
50
49
@@ -54,9 +53,9 @@ kubectl -n pgo get secret pgo.tls -o 'go-template={{ index .data "tls.key" | bas
54
53
```
55
54
56
55
57
-
## Step 4: Setup PostgreSQL Operator User
56
+
## Step 4: Setup PGO User
58
57
59
-
The PostgreSQL Operator implements its own role-based access control (RBAC) system for authenticating and authorization PostgreSQL Operator users access to its REST API. A default PostgreSQL Operator user (aka a "pgouser") is created as part of the marketplace installation (these credentials are set during the marketplace deployment workflow).
58
+
PGO implements its own role-based access control (RBAC) system for authenticating and authorization PostgreSQL Operator users access to its REST API. A default PostgreSQL Operator user (aka a "pgouser") is created as part of the marketplace installation (these credentials are set during the marketplace deployment workflow).
60
59
61
60
Create the pgouser file in `${HOME?}/.pgo/<operatornamespace>/pgouser` and insert the user and password you created on deployment of the PostgreSQL Operator via GCP Marketplace. For example, if you set up a user with the username of `username` and a password of `hippo`:
62
61
@@ -67,7 +66,7 @@ username:hippo
67
66
68
67
## Step 5: Setup Environment variables
69
68
70
-
The PostgreSQL Operator Client uses several environmental variables to make it easier for interfacing with the PostgreSQL Operator.
69
+
The `pgo`Client uses several environmental variables to make it easier for interfacing with the PGO, the Postgres Operator.
71
70
72
71
Set the environmental variables to use the key / certificate pair that you pulled in Step 3 was deployed via the marketplace. Using the previous examples, You can set up environment variables with the following command:
73
72
@@ -98,23 +97,23 @@ source ~/.bashrc
98
97
**NOTE**: For macOS users, you must use `~/.bash_profile` instead of `~/.bashrc`
99
98
100
99
101
-
## Step 6: Install the PostgreSQL Operator Client `pgo`
100
+
## Step 6: Install the `pgo` Client
102
101
103
-
The [`pgo` client](/pgo-client/) provides a helpful command-line interface to perform key operations on a PostgreSQL Operator, such as creating a PostgreSQL cluster.
102
+
The [`pgo` client](/pgo-client/) provides a helpful command-line interface to perform key operations on a PGO Deployment, such as creating a PostgreSQL cluster.
104
103
105
104
The `pgo` client can be downloaded from GitHub [Releases](https://github.com/crunchydata/postgres-operator/releases) (subscribers can download it from the [Crunchy Data Customer Portal](https://access.crunchydata.com)).
106
105
107
-
Note that the `pgo` client's version must match the version of the PostgreSQL Operator that you have deployed. For example, if you have deployed version {{< param operatorVersion >}} of the PostgreSQL Operator, you must use the `pgo` for {{< param operatorVersion >}}.
106
+
Note that the `pgo` client's version must match the deployed version of PGO. For example, if you have deployed version {{< param operatorVersion >}} of the PostgreSQL Operator, you must use the `pgo` for {{< param operatorVersion >}}.
108
107
109
108
Once you have download the `pgo` client, change the permissions on the file to be executable if need be as shown below:
110
109
111
110
```shell
112
111
chmod +x pgo
113
112
```
114
113
115
-
## Step 7: Connect to the PostgreSQL Operator
114
+
## Step 7: Connect to PGO
116
115
117
-
Finally, let's see if we can connect to the PostgreSQL Operator from the `pgo` client. In order to communicate with the PostgreSQL Operator API server, you will first need to set up a [port forward](https://kubernetes.io/docs/tasks/access-application-cluster/port-forward-access-application-cluster/) to your local environment.
116
+
Finally, let's see if we can connect to the Postgres Operator from the `pgo` client. In order to communicate with the PGO API server, you will first need to set up a [port forward](https://kubernetes.io/docs/tasks/access-application-cluster/port-forward-access-application-cluster/) to your local environment.
118
117
119
118
In a new console window, run the following command to set up a port forward:
120
119
@@ -137,7 +136,7 @@ pgo-apiserver version {{< param operatorVersion >}}
137
136
138
137
## Step 8: Create a Namespace
139
138
140
-
We are almost there! You can optionally add a namespace that can be managed by the PostgreSQL Operator to watch and to deploy a PostgreSQL cluster into.
139
+
We are almost there! You can optionally add a namespace that can be managed by PGO to watch and to deploy a PostgreSQL cluster into.
141
140
142
141
```shell
143
142
pgo create namespace wateringhole
@@ -194,4 +193,3 @@ cluster : hippo
194
193
```
195
194
196
195
The `pgo test` command provides you the basic information you need to connect to your PostgreSQL cluster from within your Kubernetes environment. For more detailed information, you can use `pgo show cluster -n wateringhole hippo`.
0 commit comments