Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -35,7 +35,7 @@ The Operator is developed and tested on CentOS and RHEL linux platforms but is k

If you are new to the Crunchy PostgreSQL Operator and interested in installing the Crunchy PostgreSQL Operator in your environment, please start here:
- [Installation via Bash](https://access.crunchydata.com/documentation/postgres-operator/4.0.0/installation/operator-install/)
- [Installation via Ansible](https://access.crunchydata.com/documentation/postgres-operator/4.0.0/gettingstarted/install-with-ansible/)
- [Installation via Ansible](https://access.crunchydata.com/documentation/postgres-operator/4.0.0/installation/install-with-ansible/)

If you have the Crunchy PostgreSQL Operator installed in your environment, and are interested in installation of the client interface, please start here:
[PGO Client Install](https://access.crunchydata.com/documentation/postgres-operator/4.0.0/installation/install-pgo-client/)
Expand Down
2 changes: 1 addition & 1 deletion hugo/content/Installation/install-with-ansible/_index.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ weight: 1
# Crunchy Data PostgreSQL Operator Playbooks

The Crunchy Data PostgreSQL Operator Playbooks contain [Ansible](https://www.ansible.com/)
roles for installing and managing the [Crunchy Data PostgreSQL Operator](https://crunchydata.github.io/postgres-operator/stable/).
roles for installing and managing the [Crunchy Data PostgreSQL Operator](https://access.crunchydata.com/documentation/postgres-operator/4.0.0/installation/install-with-ansible/).

## Features

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -217,7 +217,7 @@ database in a new PostgreSQL cluster is provisioned in the same zone as the node
containing the PostgreSQL primary pod that will be using it.

For instructions on setting up storage classes for multi-zone environments, see
the [PostgreSQL Operator Documentation](https://crunchydata.github.io/postgres-operator/stable/design/).
the [PostgreSQL Operator Documentation](https://access.crunchydata.com/documentation/postgres-operator/4.0.0/gettingstarted/design/designoverview/).

### Examples

Expand Down
48 changes: 7 additions & 41 deletions hugo/content/gettingstarted/_index.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,46 +5,12 @@ draft: false
weight: 2
---

Operator users typically will just need to install the *pgo* client
in order to work with an already deployed Postgres Operator.
If you are new to the Crunchy PostgreSQL Operator and interested in installing the Crunchy PostgreSQL Operator in your environment, please start here:
- [Installation via Bash](https://access.crunchydata.com/documentation/postgres-operator/4.0.0/installation/operator-install/)
- [Installation via Ansible](https://access.crunchydata.com/documentation/postgres-operator/4.0.0/installation/install-with-ansible/)

For installing the Operator on the Kubernetes server, see
the [Installation Guide](https://crunchydata.github.io/postgres-operator/stable/installation/).
If you have the Crunchy PostgreSQL Operator installed in your environment, and are interested in installation of the client interface, please start here:
- [PGO Client Install](https://access.crunchydata.com/documentation/postgres-operator/4.0.0/installation/install-pgo-client/)

### pgo Client Installation

The *pgo* binary is pre-compiled and available to download from the projects
github repository [Releases](https://github.com/crunchydata/postgres-operator) page.

Add the *pgo* binary to your PATH and make it executable.

Next, create a *.pgouser* file in your $HOME directory or
set the PGOUSER environment variable to point to a *.pgouser*
file location:

export PGOUSER=/somepath/.pgouser

Alternatively, if you create a *.pgouser* file in your $HOME, the *pgo*
client will find the file there.

Set the name of the Kubernetes namespace that you want to
access, on a Linux host you would enter:

export PGO_NAMESPACE=pgouser1

Set the URL of the Operator REST API, in this example the Operator is running
on a host with IP address 192.168.0.120, see your administrator for
the correct IP address, on a Linux host you would enter:

export PGO_APISERVER_URL=https://192.168.0.120:8443

Next, add the TLS keys required for the *pgo* client to connect to the
Operator REST API, see your administrator for access to these keys, on a Linux host you would enter:

export PGO_CA_CERT=/somepath/someserver.crt
export PGO_CLIENT_CERT=/somepath/someserver.crt
export PGO_CLIENT_KEY=/somepath/someserver.key

Lastly, test out the connection:

pgo version
If you have the Crunchy PostgreSQL and Client Interface installed in your environment and are interested in guidance on the use of the Crunchy PostgreSQL Operator, please start here:
- [PGO CLI Overview](https://access.crunchydata.com/documentation/postgres-operator/4.0.0/operatorcli/pgo-overview/)
2 changes: 1 addition & 1 deletion hugo/content/operatorcli/pgo-overview.md
Original file line number Diff line number Diff line change
Expand Up @@ -386,7 +386,7 @@ into your Postgres cluster pod as follows:
Note: backend metric storage such as Prometheus and front end
visualization software such as Grafana are not created automatically
by the PostgreSQL Operator. For instructions on installing Grafana and
Prometheus in your environment, see the [Crunchy Container Suite documentation](http://crunchydata.github.io/crunchy-containers/stable/examples/metrics/metrics/).
Prometheus in your environment, see the [Crunchy Container Suite documentation](https://access.crunchydata.com/documentation/crunchy-containers/2.4.0/examples/metrics/metrics/).

### Scheduled Tasks

Expand Down