Page Comparison

1. Ensure that a separate subnet is attached to it with delegation (Microsoft.DBforPostgreSWL/flexibleServers and service endpoints Storage, KeyVault, SQL, and Web).

2. If using an existing Azure Database for Postgres Flexible Server Contributor role permission must be attached to managed identity on resource level to start/stop Postgres Flexible server through scheduling.

3. A flexible server must be used in the same resource group and region in which other resources of the Kyvos cluster are deployed. If the Flexible Server is not in the same resource group, the Start and Stop functionality during scheduling will not work.

4. To use an externally created Flexible Server in deployments, use the ARM template (FlexibleServerKyvosManagerRepository and FlexibleServerKyvosRepository available in the Azure Installation files folder) to create a Flexible Server that can be used directly in the deployments.
   OR
   you can also create Flexible Server version 16 (supported for both new deployments and upgrades) through Microsoft, then you need to complete the following steps. For more information about how to create Flexible Server, refer to Microsoft documentation.

   1. For Kyvos repository

      1. The database name must be delverepo.

      2. The username must be postgres

      3. The following tags are expected on the external repository:
         UsedBy - Kyvos
         ROLE - DATABASE
         LAYER - Metadata_Storage

   2. For Kyvos Manager repository

      1. Database name must be kmrepo.

      2. Username must be kmdbuser

      3. Following tags are expected on the external repository:
         UsedBy - Kyvos
         ROLE - DATABASE_KM
         LAYER - Metadata_Storage

...