Alessandro Cattapan
Alessandro Cattapan
**Describe the bug** We are using the Pega Customer Strategic app with the CTI integration over https, which requires to explicit a dedicated port for receiving the “events” from the...
**Describe the bug** Pega helm chart v2.2.0 is not working on GKE. The all the pods start well and once Pega is up and running, Pega shuts down... This process...
**Describe the bug** We are not able to set a custom fsgroup in the securityContext of the helm chart, in fact it is always overriden by the default value 0....
**Describe the bug** Since our kubernetes cluster contains both linux and windows worker nodes, we would like to have the possibility to add a node selector also for the installer...
**Describe the bug** We are not able to pass a custom storage class for the search volumeClaim and our volume claim systems needs this configuration parameter. This prevents us from...
**Describe the bug** The web and stream ingresses does not redirect the traffic to the correct pod, in fact the URL "domainname"/c11n does not redirect the requests towards the constellations...
We have a deployment of Pega in GKE and we are noticing that a lot of the client requests towatds the Pega backend servers were being dropped because of the...
Added pod affinity support in: - Pega chart for deployment of: - Hazelcast - Elasticsearch (for Pega < 8.6) - Tiers pods - Install / Upgrade jobs - BackingServices chart...
**Describe the bug** Since the fact that the constellation messaging service does not have the livenessProbe and the readinessProbe, it cannot be delivered to our production environment **To Reproduce** Use...
**Describe the bug** The constellation and the constellation messaging services cannot be deployed to a GKE environment as they do not configure the ingresses in the right way. They entirely...