Alessandro Cattapan

Hi @RyanStan, We don't use openshift and we need a custom fsgroup in order to use a supplementary group for accessing an NFS storage volume.

Yes, sure. I have removed the confidential data ```yaml --- global: # This values.yaml file is an example. For more information about # each configuration option, see the project readme....

Hi @pega-sagas1, we still having the problem, I will share the logs with you as soon as I can. If I try to upgrade the deployment right now I will...

Yes sure: Filestore-StorageClass.yaml ```yaml apiVersion: storage.k8s.io/v1 kind: StorageClass metadata: name: filestore-standard annotations: components.gke.io/component-name: filestorecsi components.gke.io/component-version: 0.4.18 components.gke.io/layer: addon provisioner: filestore.csi.storage.gke.io parameters: tier: standard network: "projects/pocpega/global/networks/vpc-pocpega" reserved-ip-range: net-pocpega allowVolumeExpansion: true reclaimPolicy:...

We are integrating our Customer Service application with AACC (Avaya Aura Contact Center) and the suggested port by Pega to handle all the events from Avaya is 8443. The problem...

At the end we used port 443 also for the AACC communication, and until now it is working fine!

The issue is still present in the v.3.1.0 chart, have you added the possibility to change the storage class of the volume claims associated to the search pod?

Ok, thank you, and where is the right place to set the storage size for the search pods? because the: volumeClaimTemplate.resources.requests.storage under the pegasearch part of the chart is not...

Hi [kishorv10](https://github.com/kishorv10), yes I am

@MadhuriArugula unit tests created for every deployment modified and updated branch with the last changes from the master