Question
Misumi
JP
Last activity: 24 Jun 2024 8:29 EDT
Several questions about the version of helm charts and its pega support
[Backgourd]
We are using helm chart to install Pega on AWS EKS as per the reference from the page below: https://pegasystems.github.io/pega-helm-charts/
Now EKS, Pega and Helm Charts versions are as follows.
EKS: v.1.28 Pega: v8.8.2 Helm Charts: v3.6.0
Note: it is assumed that the version upgrade of Pega will not be carried out and will continue to use the current version 8.8.2 even if the EKS and Helm Charts have been upgrade to the next version.
[Question 1]
Do we have to keep the Helm Charts version to v3.6.0 in order to keep on using Pega v8.8.2?
Or the version of Helm Charts above v3.6.0 (ex. v3.22.0) will also support the installation of Pega v8.8.2?
While we tried to use Helm Charts v3.22.0 to install Pega v8.8.2, we got the follwoing errors:
[Backgourd]
We are using helm chart to install Pega on AWS EKS as per the reference from the page below: https://pegasystems.github.io/pega-helm-charts/
Now EKS, Pega and Helm Charts versions are as follows.
EKS: v.1.28 Pega: v8.8.2 Helm Charts: v3.6.0
Note: it is assumed that the version upgrade of Pega will not be carried out and will continue to use the current version 8.8.2 even if the EKS and Helm Charts have been upgrade to the next version.
[Question 1]
Do we have to keep the Helm Charts version to v3.6.0 in order to keep on using Pega v8.8.2?
Or the version of Helm Charts above v3.6.0 (ex. v3.22.0) will also support the installation of Pega v8.8.2?
While we tried to use Helm Charts v3.22.0 to install Pega v8.8.2, we got the follwoing errors:
WARNING: package com.ibm.lang.management.internal not in jdk.management 02-Feb-2024 06:27:00.047 WARNING [main] org.apache.catalina.startup.Catalina.parseServerXml Unable to load server configuration from [/usr/local/tomcat/conf/server.xml] java.io.FileNotFoundException: /usr/local/tomcat/conf/server.xml (No such file or directory) at java.base/java.io.FileInputStream.open0(Native Method) at java.base/java.io.FileInputStream.open(FileInputStream.java:219) at java.base/java.io.FileInputStream.<init>(FileInputStream.java:157) at java.base/java.io.FileInputStream.<init>(FileInputStream.java:112) at java.base/sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:86) at java.base/sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:184) at org.apache.catalina.startup.CatalinaBaseConfigurationSource.getResource(CatalinaBaseConfigurationSource.java:118) at org.apache.tomcat.util.file.ConfigurationSource.getConfResource(ConfigurationSource.java:150) at org.apache.tomcat.util.file.ConfigurationSource.getServerXml(ConfigurationSource.java:127) at org.apache.catalina.startup.CatalinaBaseConfigurationSource.getServerXml(CatalinaBaseConfigurationSource.java:52) at org.apache.catalina.startup.Catalina.parseServerXml(Catalina.java:606) at org.apache.catalina.startup.Catalina.load(Catalina.java:709) at org.apache.catalina.startup.Catalina.load(Catalina.java:746) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:307) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:477) 02-Feb-2024 06:27:00.051 SEVERE [main] org.apache.catalina.startup.Catalina.start Cannot start server, server instance is not configured
If the anwser of question 1 is NO, please continue to anwser the followings:
[Question2]
https://pegasystems.github.io/pega-helm-charts/
As per the contents of the above page, the helm charts support running on Kubernetes releases that are in Maintenance and Active
Support at the time of the helm chart’s release.
Currently, the version of Helm Charts used in the staging/production environment is v3.6.0 released in 2023/9.
The latest version released in k8s/EKS at this time is v1.28, so is it true that this version is supported by Pega Support Center?
[Question3]
If we keep on using Pega v8.8.2 and Helm charts v3.6.0, while the EKS is upgraded from v1.28 to v1.29, can we still get support from Pega Support Center if there is any problems with the system?
[Question 4]
If we don't update the version of Pega and Helm Charts from v3.6.0, is it better not to update the version of EKS from v1.28? Please share your opinions about this.
Accepted Solution
Updated: 24 Jun 2024 8:29 EDT
Pegasystems Inc.
US
@JiarongD17057703The latest chart version should support any Pega Platform version. The docker images are updated regularly with security fixes and changes required for newer versions of the Helm chart. This means that if you pull the same 8.8.2 tag today, it may have some changes that would require updating your chart. And similarly, if you get the latest version of the chart you may need to pull your image tag again to ensure it's compatible with that chart version.
I'd suggest you first re-tag your existing image in your registry (so you have that version available if you want to revert back to chart 3.6.0). Then pull the latest build of tag 8.8.2 and check if that resolves the error you saw.
The other step you should consider when upgrading your chart is to compare the values file of your current version to the one in the upgraded version. For example, in your case, check pega/values.yaml: https://github.com/pegasystems/pega-helm-charts/compare/v3.6.0...v3.22.0?diff=split&w= There are a decent number of updates to the values file. Some are new configuration options, other's are breaking changes like service.external_secret_name changed to service.external_secret_names.