About the PegaPlatform container image version upgrade cycle

I am currently using 8.7 and am considering upgrading to 24.1.

Since containerization of Pega is required, please confirm the version update policy related to containers.

How often are Pega’s container images and Helm charts updated?

Also, please check whether it is necessary to upgrade the Pega version along with the Kubernetes version update.

Some information is available on the Pegasystems Helm Charts Readme ‘runbooks’ page.

According to the Containerized deployments FAQs documentation :

Pega-provided Docker images

@casad can you offer some insight on this question?

Also the link pointing to "https://community.pega.com/knowledgebase/articles/cloud-choice" is broken as it redirects to our legacy docs-previous server.

→ Please could you find out who can update this Github page to have it point to the correct Cloud Choice documentation?

Client-managed Cloud

Cloud Choice Matters: A Guide to Selecting the Right Cloud

Pega-provided Docker images

Containerized deployments in Kubernetes environments

Deployment requirements for client-managed cloud

@ShinyaS17291522

The versioning policy for the Pega Helm Charts is described on Github.

Kubernetes Version support is also explained on Github

“The helm charts support running on Kubernetes releases that are in Maintenance and Active Support at the time of the helm chart’s release.”

Rule of thumb:

  • When upgrading the Infinity version, always move to the latest Pega Helm Charts & images.
  • When upgrading Kubernetes, also upgrade the Pega Helm Charts to a release that supports the target Kubernetes version.
  • When upgrading the Pega Helm Charts, also move to the latest images.
  • Images should be updated frequently to remediate CVEs.