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
- GCR Service Account JSON `sa.json` (provided by Codefresh, contact support@codefresh.io)
34
34
- Firebase url and secret
35
35
- Valid TLS certificates for Ingress
36
-
- When external PostgreSQL is used, `pg_cron` and `pg_partman` extensions **must be enabled** for [analytics](https://codefresh.io/docs/docs/dashboards/pipeline-analytics/#content) to work (see [AWS RDS example](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/PostgreSQL_pg_cron.html#PostgreSQL_pg_cron.enable))
36
+
- When [external](#external-postgressql) PostgreSQL is used, `pg_cron` and `pg_partman` extensions **must be enabled** for [analytics](https://codefresh.io/docs/docs/dashboards/pipeline-analytics/#content) to work (see [AWS RDS example](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/PostgreSQL_pg_cron.html#PostgreSQL_pg_cron.enable))
37
37
38
38
## Get Repo Info and Pull Chart
39
39
@@ -686,7 +686,7 @@ This major chart version change (v1.4.X -> v2.0.0) contains some **incompatible
686
686
687
687
#### ⚠️ New MongoDB Indexes
688
688
689
-
Starting from version 2.0.0, two new MongoDB indexes have been adedd that are vital for optimizing database queries and enhancing overall system performance. It is crucial to create these indexes before performing the upgrade to avoid any potential performance degradation.
689
+
Starting from version 2.0.0, two new MongoDB indexes have been added that are vital for optimizing database queries and enhancing overall system performance. It is crucial to create these indexes before performing the upgrade to avoid any potential performance degradation.
@@ -709,7 +709,7 @@ Starting from version 2.0.0, two new MongoDB indexes have been adedd that are vi
709
709
710
710
To prevent potential performance degradation during the upgrade, it is important to schedule a maintenance window during a period of low activity or minimal user impact and create the indexes mentioned above before initiating the upgrade process. By proactively creating these indexes, you can avoid the application automatically creating them during the upgrade and ensure a smooth transition with optimized performance.
711
711
712
-
##### Index Creation
712
+
**Index Creation**
713
713
714
714
If you're hosting MongoDB on [Atlas](https://www.mongodb.com/atlas/database), use the following [Create, View, Drop, and Hide Indexes](https://www.mongodb.com/docs/atlas/atlas-ui/indexes/) guide to create indexes mentioned above. It's important to create them in a rolling fashion (i.e. **Build index via rolling process** checkbox enabled) in produciton environment.
@@ -1052,6 +1052,7 @@ The bare minimal workload footprint for the new services (without HPA or PDB) is
1052
1052
| global.postgresHostname | string | `""` | Set External Postgresql service address. Takes precedence over `global.postgresService`. See "External Postgresql" example below. |
1053
1053
| global.postgresPassword | string | `"eC9arYka4ZbH"` | Default Postgresql password (from bitnami/postgresql subchart). Change if you use external PostreSQL. See "External Postgresql" example below. |
1054
1054
| global.postgresPort | int | `5432` | Default Postgresql port number (from bitnami/postgresql subchart). Change if you use external PostreSQL. See "External Postgresql" example below. |
| global.postgresService | string | `"postgresql"` | Default Internal Postgresql service address (from bitnami/postgresql subchart). Change if you use external PostreSQL. See "External Postgresql" example below. |
1056
1057
| global.postgresUser | string | `"postgres"` | Default Postgresql username (from bitnami/postgresql subchart). Change if you use external PostreSQL. See "External Postgresql" example below. |
Copy file name to clipboardExpand all lines: codefresh/README.md.gotmpl
+5-4Lines changed: 5 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -33,7 +33,8 @@
33
33
- GCR Service Account JSON `sa.json` (provided by Codefresh, contact support@codefresh.io)
34
34
- Firebase url and secret
35
35
- Valid TLS certificates for Ingress
36
-
- When external PostgreSQL is used, `pg_cron` and `pg_partman` extensions **must be enabled** for [analytics](https://codefresh.io/docs/docs/dashboards/pipeline-analytics/#content) to work (see [AWS RDS example](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/PostgreSQL_pg_cron.html#PostgreSQL_pg_cron.enable))
36
+
- When [external](#external-postgressql) PostgreSQL is used, `pg_cron` and `pg_partman` extensions **must be enabled** for [analytics](https://codefresh.io/docs/docs/dashboards/pipeline-analytics/#content) to work (see [AWS RDS example](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/PostgreSQL_pg_cron.html#PostgreSQL_pg_cron.enable))
37
+
37
38
38
39
## Get Repo Info and Pull Chart
39
40
@@ -687,7 +688,7 @@ This major chart version change (v1.4.X -> v2.0.0) contains some **incompatible
687
688
688
689
#### ⚠️ New MongoDB Indexes
689
690
690
-
Starting from version 2.0.0, two new MongoDB indexes have been adedd that are vital for optimizing database queries and enhancing overall system performance. It is crucial to create these indexes before performing the upgrade to avoid any potential performance degradation.
691
+
Starting from version 2.0.0, two new MongoDB indexes have been added that are vital for optimizing database queries and enhancing overall system performance. It is crucial to create these indexes before performing the upgrade to avoid any potential performance degradation.
@@ -710,7 +711,7 @@ Starting from version 2.0.0, two new MongoDB indexes have been adedd that are vi
710
711
711
712
To prevent potential performance degradation during the upgrade, it is important to schedule a maintenance window during a period of low activity or minimal user impact and create the indexes mentioned above before initiating the upgrade process. By proactively creating these indexes, you can avoid the application automatically creating them during the upgrade and ensure a smooth transition with optimized performance.
712
713
713
-
##### Index Creation
714
+
**Index Creation**
714
715
715
716
If you're hosting MongoDB on [Atlas](https://www.mongodb.com/atlas/database), use the following [Create, View, Drop, and Hide Indexes](https://www.mongodb.com/docs/atlas/atlas-ui/indexes/) guide to create indexes mentioned above. It's important to create them in a rolling fashion (i.e. **Build index via rolling process** checkbox enabled) in produciton environment.
0 commit comments