Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Best practices for managing secrets

Updated on May 12, 2020

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:

Type

Configuration Example

Credentials using environment variables

env:

- name: DB_USERNAME

- valueFrom:

- secretKeyRef:

- name: mysecret

key: username

- name: DB_PASSWORD

- valueFrom:

secretKeyRef:

- name: mysecret

- key: password

Credentials using volume mount

containers:

...

volumeMounts:

- name: secret-volume

- mountPath: /opt/pega/secrets

volumes:

- name: secret-volume

secret:

- secretName: mysecret

Docker registry secret

imagePullSecrets:

- name: regsecret

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us