@@ -90,17 +90,17 @@ It is up to the user to ensure there is no collision between operators.
90
90
91
91
## Deployment of the EDB Postgres Distributed for Kubernetes operator (PG4K-PGD)
92
92
93
- Like PG4K install, both the operator and the operand images required by PG4K-PGD
94
- may be pulled from the ` k8s_enterprise ` or ` k8s_standard ` repositories at
95
- ` docker.enterprisedb.com ` , please obtaining an EDB subscription token before setup.
93
+ Like PG4K helm chart install, both the operator and the operand images required
94
+ by ` edb-postgres-distributed-for-kubernetes ` may be pulled from the
95
+ ` k8s_enterprise_pgd ` or ` k8s_standard_pgd ` repositories at ` docker.enterprisedb.com ` ,
96
+ please obtaining an EDB subscription token before setup.
96
97
97
- The ` edb-postgres-distributed-for-kubernetes ` chart will by default install PG4K
98
- operator defined by sub-chart in the same namespace, the PG4K operator installed
99
- in the sub-chart is PG4K LTS release operator, which is upgraded along with the
100
- parent chart version release.
98
+ The PG4K-PGD chart installs both the PG4K-PGD and PG4K operators in the
99
+ same namespace. The PG4K operator installed is a stable version that is
100
+ part of the latest long-term support release of PG4K.
101
101
102
- The ` edb-postgres-distributed-for-kubernetes ` chart also install the cert-manager
103
- operators as dependency. You can avoid this if necessary. See the sub-section
102
+ The PG4K-PGD chart also install the cert-manager operators as dependency. You
103
+ can avoid this if necessary. See the sub-section
104
104
[ on deploying individually] ( #deploying-the-PG4K-PGD-operators-individually ) .
105
105
106
106
** Note:** this helm chart uses a default registry to retrieve the operator
@@ -145,7 +145,7 @@ helm chart are working:
145
145
### Deploying the PG4K-PGD operators and cert-manager individually
146
146
147
147
The chart ` edb-postgres-distributed-for-kubernetes ` is set by default to
148
- also install PG4K and cert-manager operators, which it depends on.
148
+ also install cert-manager operators, which it depends on.
149
149
When following this route, all operators will be installed in the same
150
150
namespace. This is in contrast with other installation paths, where the
151
151
operators reside in dedicated namespaces.
@@ -154,7 +154,7 @@ Installing all dependencies in the same namespace is a design limitation of
154
154
Helm, but we can get around it by installing dependencies with separate
155
155
invocations of ` helm ` .
156
156
157
- If you would like to install the cert-manager in separate namespaces, please
157
+ If you would like to install the cert-manager in a separate namespaces, please
158
158
follow the below steps.
159
159
160
160
#### 1. Setup cert-manager
@@ -184,23 +184,10 @@ In case you choose this option, remember to also specify
184
184
` --set cert-manager.enabled=false ` during the installation of the PG4K-PGD
185
185
helm chart in the next section.
186
186
187
- #### 2. Setup PG4K
188
-
189
- By default, a PG4K operator with LTS release is installed alongside with PG4K-PGD
190
- deploy. You can follow [ PG4K helm chart] ( #deployment-of-the-edb-postgres-for-kubernetes-operator-pg4k )
191
- to deploy the PG4K operator in its own namespace. But it is highly recommended to use
192
- the PG4K operator installed as dependency of PG4K-PGD chart, which contains the well tested PG4K
193
- operator version.
194
-
195
- In case you choose to use existing PG4K operator, remember to also specify
196
- ` --set edb-postgres-for-kubernetes-lts.enabled=false ` during the installation of the PG4K-PGD
197
- helm chart in the next section.
198
-
199
- #### 3. Setup PG4K-PGD
187
+ #### 2. Setup PG4K-PGD
200
188
201
189
Once the above deployments are ready, you can deploy the PG4K-PGD helm chart. taking care
202
- to set ` edb-postgres-for-kubernetes-lts.enabled ` to false if you PG4K already deployed,
203
- and set ` cert-manager.enabled ` to false if cert-manager is installed separately.
190
+ to set ` cert-manager.enabled ` to false if cert-manager is installed separately.
204
191
205
192
** Note:** in the following example, the flags setting the credentials were elided
206
193
to put the focus on the ` enabled=false ` condition. The flags may still be
@@ -213,19 +200,17 @@ helm upgrade --dependency-update \
213
200
--create-namespace \
214
201
edb/edb-postgres-distributed-for-kubernetes \
215
202
--set cert-manager.enabled=false
216
- --set edb-postgres-for-kubernetes-lts.enabled=false
217
203
```
218
204
219
- You can see the three separate namespaces, the same that would be created if
220
- installing manually without Helm charts .
205
+ You can see two seperate namespaces where cert-manager is installed in ` cert-manager `
206
+ namespaces .
221
207
222
208
``` sh
223
209
$ kubectl get ns
224
210
NAME STATUS AGE
225
211
…
226
212
cert-manager Active 24m
227
213
pgd-operator-system Active 55s
228
- postgresql-operator-system Active 5m33s
229
214
```
230
215
231
216
### Controlling the image repositories
@@ -238,14 +223,12 @@ subscription plan. This needs to be done in several places in the command-line
238
223
invocation.
239
224
240
225
The following example uses the ` k8s_standard_pgd ` registry in
241
- ` docker.enterprisedb.com ` .
242
- Note the multiple ` --set ` options, for the ` image.repository ` ,
243
- ` PGD_IMAGE_NAME ` and ` PGD_PROXY_IMAGE_NAME ` in addition to the
244
- ` edb-postgres-for-kubernetes-lts.image.repository ` where the PGD operator
245
- is pulled from. There are 4 in total
246
- - ` image.repository ` where the PG4K-PGD operator image is pulled from.
247
- - ` edb-postgres-for-kubernetes-lts.image.repository ` where the PG4K operator image is pulled from.
248
- - ` PGD_IMAGE_NAME ` and ` PGD_PROXY_IMAGE_NAME ` where the PGD and PGD Proxy image are pulled from.
226
+ ` docker.enterprisedb.com ` . Following is the description of set options.
227
+ - ` global.image.repository ` : The repository where the PG4K-PGD and PG4K operator image downloaded from.
228
+ This is a global setting, which is shared for both PG4K-PGD and PG4K operators.
229
+ - ` PGD_IMAGE_NAME ` : The location where the PGD image are pulled from.
230
+ - ` PGD_PROXY_IMAGE_NAME ` : The location where PGD Proxy image are pulled from, usually
231
+ the same with ` PGD_IMAGE_NAME ` .
249
232
250
233
Assuming that you have your necessary credentials, please fill in the USERNAME
251
234
and PASSWORD below.
@@ -258,8 +241,7 @@ helm upgrade --dependency-update \
258
241
edb/edb-postgres-distributed-for-kubernetes \
259
242
--set image.imageCredentials.username=${USERNAME} \
260
243
--set image.imageCredentials.password=${PASSWORD} \
261
- --set image.repository=docker.enterprisedb.com/k8s_standard_pgd/pg4k-pgd \
262
- --set edb-postgres-for-kubernetes-lts.image.repository=docker.enterprisedb.com/k8s_standard_pgd/edb-postgres-for-kubernetes \
244
+ --set global.image.repository=docker.enterprisedb.com/k8s_standard_pgd \
263
245
--set config.data.PGD_IMAGE_NAME=docker.enterprisedb.com/k8s_standard_pgd/postgresql-pgd:15.6-5.5.1-1 \
264
246
--set config.data.PGD_PROXY_IMAGE_NAME=docker.enterprisedb.com/k8s_standard_pgd/edb-pgd-proxy:5.5.0
265
247
```
0 commit comments