I am doing an install in Kubernetes on AKS and am receiving the following error:

[java] Caused by: com.pega.pegarules.pub.database.ConfigurationException: Database-General    PegaDATA is not defined in the prconfig settings for this system.  Please ensure that PegaDATA is defined with either datasource or url based connection information

[java] Caused by: com.pega.pegarules.pub.PRRuntimeException: Error determining the mode of PRPC install from database.

This is on an empty database, where the installation runs for approximately 15 minutes and then fails with that error. I noticed this error:

This is likely due to using a copy of prconfig.xml from a previous install.

However, that is not the case as there has not been a previous installation performed on the environment (I even recreated the Kubernetes cluster from scratch).

I rebuilt the cluster and the database and tried Pega 8.5.2, 8.5.3 and 8.6.0 images with the same result.

I followed the instructions from here:

https://github.com/pegasystems/pega-helm-charts/blob/master/docs/Deploying-Pega-on-AKS.md

I did not make any changes to the default `prconfig.xml` and am allowing the system to configure it on its own. Do I need to do anything specialize here?

I see at the start of the logs it gets dynamically generated:

Generating prconfig.xml from templates.

This completely blocks deployment to all environments.

Based on the logs attached it seems that the generated `prconfig.xml` file gets generated improperly:

org.xml.sax.SAXParseException: The reference to entity "GL6" must end with the ';' delimiter.

The JDBC connection string must be good because:

• I am using it to execute a database migration to create the schemas
• I see in the attached logs that the tables are created properly in the databse
• I am able to log into the database manually and see the tables that were created

Steps Followed

1. Create AKS cluster
2. Create database instance (MSSQL)
3. Generate `values.yml` from the Helm instructions
4. Update the YAML configuration with the appropriate database information, schema data, etc.
5. Create the schema and other initialization data required in the database
6. Execute the helm script using `helm upgrade --install --debug --wait --timeout 3h MY_DEPLOY -f /path/to/values.yaml --set global.actions.execute=install .` (additional parameters used to dynamically provide JDBC information)
7. Allow install to run (dies consistently after 15 minutes)

Additional Data

Logs attached with connection details removed.

• Helm Chart Version: 1.5.3
• Helm Version: 3.5.4
• Pega Version: 8.6.0