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/guides/private-registries.md
+23-10Lines changed: 23 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,15 +5,22 @@ draft: false
5
5
weight: 200
6
6
---
7
7
8
-
PGO, the open source Postgres Operator, can use containers that are stored in private registries. There are a variety of techniques that are used to load containers from private registries, including [image pull secrets](https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/). This guide will demonstrate how to install PGO and deploy a Postgres cluster using the [Crunchy Data Customer Portal](https://access.crunchydata.com/) registry as an example.
8
+
PGO, the open source Postgres Operator, can use containers that are stored in private registries.
9
+
There are a variety of techniques that are used to load containers from private registries,
10
+
including [image pull secrets](https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/).
11
+
This guide will demonstrate how to install PGO and deploy a Postgres cluster using the
12
+
[Crunchy Data Customer Portal](https://access.crunchydata.com/) registry as an example.
9
13
10
14
## Create an Image Pull Secret
11
15
12
-
The Kubernetes documentation provides several methods for [creating image pull secrets]([image pull secrets](https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/)). You can choose the method that is most appropriate for your installation.
16
+
The Kubernetes documentation provides several methods for creating
You can choose the method that is most appropriate for your installation. You will need to create
19
+
image pull secrets in the namespace that PGO is deployed and in each namespace where you plan to
20
+
deploy Postgres clusters.
13
21
14
-
You will need to create an image pull secret in the same namespace that PGO is deployed in. You will also need to create image pull secrets in each namespace you plan to deploy Postgres clusters into.
15
-
16
-
For example, to create an image pull secret for accessing the Crunchy Data Customer Portal image registry in the `postgres-operator` namespace, you can execute the following commands:
22
+
For example, to create an image pull secret for accessing the Crunchy Data Customer Portal image
23
+
registry in the `postgres-operator` namespace, you can execute the following commands:
17
24
18
25
```shell
19
26
kubectl create ns postgres-operator
@@ -29,9 +36,12 @@ This creates an image pull secret named `crunchy-regcred` in the `postgres-opera
29
36
30
37
## Install PGO from a Private Registry
31
38
32
-
To [install PGO]({{< relref "installation/_index.md" >}}) from a private registry, you will need to set an image pull secret on the installation manifest.
39
+
To [install PGO]({{< relref "installation/_index.md" >}}) from a private registry, you will need to
40
+
set an image pull secret on the installation manifest.
33
41
34
-
For example, to set up an image pull secret using the [Kustomize install method]({{< relref "installation/_index.md" >}}) to install PGO from the [Crunchy Data Customer Portal](https://access.crunchydata.com/), you can set the following in the `install/bases/kustomization.yaml` manifest:
42
+
For example, to set up an image pull secret using the [Kustomize install method]({{< relref "installation/_index.md" >}})
43
+
to install PGO from the [Crunchy Data Customer Portal](https://access.crunchydata.com/), you can set
44
+
the following in the `install/bases/kustomization.yaml` manifest:
35
45
36
46
```yaml
37
47
images:
@@ -56,7 +66,8 @@ patchesJson6902:
56
66
- name: crunchy-regcred
57
67
```
58
68
59
-
If you are using a version of `kubectl` prior to `v1.21.0`, you will have to create an explicit patch file named `install-ops.yaml`:
69
+
If you are using a version of `kubectl` prior to `v1.21.0`, you will have to create an explicit
## Deploy a Postgres cluster from a Private Registry
96
107
97
-
To deploy a Postgres cluster using images from a private registry, you will need to set the value of `spec.imagePullSecrets` on a `PostgresCluster` custom resource.
108
+
To deploy a Postgres cluster using images from a private registry, you will need to set the value of
109
+
`spec.imagePullSecrets`on a `PostgresCluster` custom resource.
98
110
99
-
For example, to deploy a Postgres cluster using images from the [Crunchy Data Customer Portal](https://access.crunchydata.com/) with an image pull secret in the `postgres-operator` namespace, you can use the following manifest:
111
+
For example, to deploy a Postgres cluster using images from the [Crunchy Data Customer Portal](https://access.crunchydata.com/)
112
+
with an image pull secret in the `postgres-operator` namespace, you can use the following manifest:
0 commit comments