docs(postgresql): mention potential SSL issues in “To 2.8” section

Author: masontikhonov

codefresh/README.md

@@ -424,10 +424,10 @@ helm-repo-manager:
     POSTGRES_DISABLE_SSL: "false"
 ```
 
-> ⚠️ **Important!**
+> ⚠️ **Important!**<br />
 > We do not support custom CA configuration for PostgreSQL, including self-signed certificates. This may cause incompatibility with some providers' default configurations.<br />
 > In particular, Amazon RDS for PostgreSQL version 15 and later requires SSL encryption by default ([ref](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/PostgreSQL.Concepts.General.SSL.html#PostgreSQL.Concepts.General.SSL.Requiring)).<br />
-> We recommend disabling SSL on the provider side in such cases or using the following workaround to mount custom CA certificates: [Mounting private CA certs](#mounting-private-ca-certs)
+> We recommend disabling SSL on the provider side in such cases or using the following steps to mount custom CA certificates: [Mounting private CA certs](#mounting-private-ca-certs)
 
 #### External Redis
 
@@ -2185,6 +2185,10 @@ Default PostgreSQL image is changed from 13.x to 17.x
 
 If you run external PostgreSQL, follow the [official instructions](https://www.postgresql.org/docs/17/upgrading.html) to upgrade to 17.x.
 
+> ⚠️ **Important!**<br />
+> The default SSL configuration may change on your provider's side when you upgrade.<br />
+> Please read the following section before the upgrade: [Using SSL with a PostgreSQL](#using-ssl-with-a-postgresql)
+
 ⚠️ ⚠️ ⚠️  16.x version is also supported (17.x version of PostgreSQL is still in preview on multiple cloud providers)
 
 ⚠️ ⚠️ ⚠️ If you run built-in PostgreSQL `bitnami/postgresql` subchart, direct upgrade is not supported due to **incompatible breaking changes** in the database files. You will see the following error in the logs:

codefresh/README.md.gotmpl

@@ -426,10 +426,10 @@ helm-repo-manager:
     POSTGRES_DISABLE_SSL: "false"
 ```
 
-> ⚠️ **Important!**
+> ⚠️ **Important!**<br />
 > We do not support custom CA configuration for PostgreSQL, including self-signed certificates. This may cause incompatibility with some providers' default configurations.<br />
 > In particular, Amazon RDS for PostgreSQL version 15 and later requires SSL encryption by default ([ref](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/PostgreSQL.Concepts.General.SSL.html#PostgreSQL.Concepts.General.SSL.Requiring)).<br />
-> We recommend disabling SSL on the provider side in such cases or using the following workaround to mount custom CA certificates: [Mounting private CA certs](#mounting-private-ca-certs)
+> We recommend disabling SSL on the provider side in such cases or using the following steps to mount custom CA certificates: [Mounting private CA certs](#mounting-private-ca-certs)
 
 
 #### External Redis
@@ -2195,6 +2195,10 @@ Default PostgreSQL image is changed from 13.x to 17.x
 
 If you run external PostgreSQL, follow the [official instructions](https://www.postgresql.org/docs/17/upgrading.html) to upgrade to 17.x.
 
+> ⚠️ **Important!**<br />
+> The default SSL configuration may change on your provider's side when you upgrade.<br />
+> Please read the following section before the upgrade: [Using SSL with a PostgreSQL](#using-ssl-with-a-postgresql)
+
 ⚠️ ⚠️ ⚠️  16.x version is also supported (17.x version of PostgreSQL is still in preview on multiple cloud providers)
 
 ⚠️ ⚠️ ⚠️ If you run built-in PostgreSQL `bitnami/postgresql` subchart, direct upgrade is not supported due to **incompatible breaking changes** in the database files. You will see the following error in the logs: