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
Due to changes in the Bitnami catalog (Ref: [Upcoming changes to the Bitnami catalog (effective August 28th, 2025)](https://github.com/bitnami/containers/issues/83267)), the following subcharts have been updated to use `docker.io/bitnamilegacy` repository:
201
+
202
+
- MongoDB
203
+
- PostgreSQL
204
+
- Redis
205
+
- RabbitMQ
206
+
- Nats
207
+
- Consul
208
+
209
+
[Bitnami Legacy repository](https://hub.docker.com/u/bitnamilegacy) catalog will receive no further updates or support and should only be used for temporary evaluation purposes. For production usage, please consider externalizing these services as described in [Configuring external services](#configuring-external-services) section.
210
+
211
+
If you have an option to use [Bitnami Secure Images](https://www.arrow.com/globalecs/uk/products/bitnami-secure-images/?utm_source=google&utm_medium=paidsearch&utm_campaign=bitnami&gad_source=1&gad_campaignid=22996675622), you need to override image repository and tag for each of Bitnami subcharts used in Codefresh chart and [provide a valid image pull secret](https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/#registry-secret-existing-credentials).
212
+
213
+
```yaml
214
+
mongodb:
215
+
image:
216
+
repository: bitnami/mongodb
217
+
tag: <version>
218
+
pullSecrets:
219
+
- my-bitnami-registry-secret
220
+
221
+
redis:
222
+
image:
223
+
repository: bitnami/redis
224
+
tag: <version>
225
+
pullSecrets:
226
+
- my-bitnami-registry-secret
227
+
228
+
postgresql:
229
+
image:
230
+
repository: bitnami/postgresql
231
+
tag: <version>
232
+
pullSecrets:
233
+
- my-bitnami-registry-secret
234
+
235
+
rabbitmq:
236
+
image:
237
+
repository: bitnami/rabbitmq
238
+
tag: <version>
239
+
pullSecrets:
240
+
- my-bitnami-registry-secret
241
+
242
+
nats:
243
+
image:
244
+
repository: bitnami/nats
245
+
tag: <version>
246
+
pullSecrets:
247
+
- my-bitnami-registry-secret
248
+
249
+
consul:
250
+
image:
251
+
repository: bitnami/consul
252
+
tag: <version>
253
+
pullSecrets:
254
+
- my-bitnami-registry-secret
255
+
```
256
+
197
257
## Chart Configuration
198
258
199
259
See [Customizing the Chart Before Installing](https://helm.sh/docs/intro/using_helm/#customizing-the-chart-before-installing). To see all configurable options with detailed comments, visit the chart's [values.yaml](./values.yaml), or run these configuration commands:
Due to changes in the Bitnami catalog (Ref: [Upcoming changes to the Bitnami catalog (effective August 28th, 2025)](https://github.com/bitnami/containers/issues/83267)), the following subcharts have been updated to use `docker.io/bitnamilegacy` repository:
202
+
203
+
- MongoDB
204
+
- PostgreSQL
205
+
- Redis
206
+
- RabbitMQ
207
+
- Nats
208
+
- Consul
209
+
210
+
[Bitnami Legacy repository](https://hub.docker.com/u/bitnamilegacy) catalog will receive no further updates or support and should only be used for temporary evaluation purposes. For production usage, please consider externalizing these services as described in [Configuring external services](#configuring-external-services) section.
211
+
212
+
If you have an option to use [Bitnami Secure Images](https://www.arrow.com/globalecs/uk/products/bitnami-secure-images/?utm_source=google&utm_medium=paidsearch&utm_campaign=bitnami&gad_source=1&gad_campaignid=22996675622), you need to override image repository and tag for each of Bitnami subcharts used in Codefresh chart and [provide a valid image pull secret](https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/#registry-secret-existing-credentials).
213
+
214
+
```yaml
215
+
mongodb:
216
+
image:
217
+
repository: bitnami/mongodb
218
+
tag: <version>
219
+
pullSecrets:
220
+
- my-bitnami-registry-secret
221
+
222
+
redis:
223
+
image:
224
+
repository: bitnami/redis
225
+
tag: <version>
226
+
pullSecrets:
227
+
- my-bitnami-registry-secret
228
+
229
+
postgresql:
230
+
image:
231
+
repository: bitnami/postgresql
232
+
tag: <version>
233
+
pullSecrets:
234
+
- my-bitnami-registry-secret
235
+
236
+
rabbitmq:
237
+
image:
238
+
repository: bitnami/rabbitmq
239
+
tag: <version>
240
+
pullSecrets:
241
+
- my-bitnami-registry-secret
242
+
243
+
nats:
244
+
image:
245
+
repository: bitnami/nats
246
+
tag: <version>
247
+
pullSecrets:
248
+
- my-bitnami-registry-secret
249
+
250
+
consul:
251
+
image:
252
+
repository: bitnami/consul
253
+
tag: <version>
254
+
pullSecrets:
255
+
- my-bitnami-registry-secret
256
+
```
257
+
258
+
198
259
## Chart Configuration
199
260
200
261
See [Customizing the Chart Before Installing](https://helm.sh/docs/intro/using_helm/#customizing-the-chart-before-installing). To see all configurable options with detailed comments, visit the chart's [values.yaml](./values.yaml), or run these configuration commands:
@@ -1599,6 +1660,9 @@ If you're hosting MongoDB on [Atlas](https://www.mongodb.com/atlas/database), us
1599
1660
> [!IMPORTANT]
1600
1661
> In Atlas, for production environments, it may be recommended to use rolling index builds by enabling the "Build index via rolling process" checkbox. ([*MongoDB official documentation*](https://www.mongodb.com/docs/v7.0/tutorial/build-indexes-on-replica-sets/))
0 commit comments