Preparing your environment to deploy Pega Platform

The following Kubernetes environments are supported. See the list of enterprise configurations and settings that are required in a supported Kubernetes environment.

Minimum environment requirements

Pega Platform supports the following versions of Kubernetes environments:




Kubernetes 1.10 or later. For details, see the Kubernetes documentation for Setup.


Red Hat OpenShift 3.10 or later. For details, see the OpenShift documentation for Planning your installation.

Amazon EKS

For details, see the AWS documentation for the Amazon EKS User Guide: Getting Started with Amazon EKS.

Google Kubernetes Engine (GKE) For details, see Google Kubernetes Engine documentation.

Pivotal Container Service (PKS)

PKS 1.2 or later. For details, see the Pivotal Container Service (PKS) documentation.

Azure Kubernetes Service (AKS)

For details, see the Azure Kubernetes Service (AKS) documentation.

Required configurations and settings

Ensure that the following configurations are completed in your environment:

  • Pega Platform database - See the list of database types that Pega Platform supports in the Platform Support Guide. This database will be used later to install Pega Platform.

  • DNS settings - You must configure domain names in your enterprise DNS servers to ensure the exposed Kubernetes services used in Pega deployments receive traffic over your network. For details, see Deploying Pega Platform with Helm.
  • URLs and credentials - you must provide the following URLs and associated credentials when you configure your deployment:
    • Your database URL and username, and password.
    • Your Docker registry URL, username, and password.
    • To use your existing Cassandra service and not deploy the Cassandra service Pega provides, you will need the URL, username, and password to access your external Cassandra node. (a Cassandra service is required for Customer Decision Hub and Pega Marketing).

Support for Kubernetes secrets

Pega supports using Kubernetes secrets to secure credentials and related information. Use secrets to represent credentials for your database, Docker registry, or any other token or key that you need to pass to a deployed application. To create a secret, follow the Kubernetes documentation for Distributing Credentials Securely Using Secrets

Pega supports passing secrets in the following ways:


Configuration Example

Credentials using environment variables



- valueFrom:

- secretKeyRef:

- name: mysecret

key: username


- valueFrom:


- name: mysecret

- key: password

Credentials using volume mount




- name: secret-volume

- mountPath: /opt/pega/secrets


- name: secret-volume


- secretName: mysecret

Docker registry secret


- name: regsecret


Suggest Edit

100% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.