Need help on the Pega Helm charts connectig to the database through kerberos
We are deploying PEGA in the client cloud, and to leverage PEGA helm charts how to connect to the database through kerberos and also during upgrade will it upgrade both Rules and Data Schema upgrade at the same time ? Currently we need to run the upgrade individually by running the upgrade with the schema corresponding DB user.
Pegasystems Inc.
GB
@satsihch When deploying Pega in a client cloud and using Pega helm charts, you can leverage the Pega-provided Docker images to deploy Pega Platform in a Kubernetes environment of your choice. For database connection through Kerberos, you would need to ensure that your cloud environment supports Kerberos authentication and that the necessary configurations are in place. As for the upgrade process, Pega recommends updating using the single migration process in which the rules schema update occurs out-of-place. This process involves four schemas: Data schema, Rules schema, a temporary data schema (Dtmp), and a new rules schema (Rn). The update process involves migrating the rules structure and content and data structure from the existing rules and data schemas to the new rules and temporary data schemas. Then, the new rules schema is updated. After that, the existing data schema is updated. So, while the rules and data schemas are not updated at the exact same time, they are part of the same overall update process.
⚠ This is a GenAI-powered tool. All generated answers require validation against the provided references.
please can you confirm that you already found the below documentation?
@satsihch When deploying Pega in a client cloud and using Pega helm charts, you can leverage the Pega-provided Docker images to deploy Pega Platform in a Kubernetes environment of your choice. For database connection through Kerberos, you would need to ensure that your cloud environment supports Kerberos authentication and that the necessary configurations are in place. As for the upgrade process, Pega recommends updating using the single migration process in which the rules schema update occurs out-of-place. This process involves four schemas: Data schema, Rules schema, a temporary data schema (Dtmp), and a new rules schema (Rn). The update process involves migrating the rules structure and content and data structure from the existing rules and data schemas to the new rules and temporary data schemas. Then, the new rules schema is updated. After that, the existing data schema is updated. So, while the rules and data schemas are not updated at the exact same time, they are part of the same overall update process.
⚠ This is a GenAI-powered tool. All generated answers require validation against the provided references.
please can you confirm that you already found the below documentation?
Updating with near-zero downtime
Installing, patching, or updating Pega software
Containerized deployments in Kubernetes environments
Configuring a containerized deployment to use a Kafka service
Virtual machine deployments of Pega Platform
Upgrading Pega Platform in your deployment with zero-downtime
Pega Customer Service Upgrade Checker
Could you clarify what is your exact question so that we might find the relevant SME to help answer this for you?