dekke046

Here same issue, also not using openshift but a company managed shared kubernetes environment. `Pods "etest-web-5b668f4db7-" is forbidden: PodSecurityPolicy: unable to admit pod: [spec.securityContext.fsGroup: Invalid value: []int64{0}: group 0 must...

@kseniaguzeeva, is this still part of development or completely dropped?

Since the last big upgrade of Colima I experience the same. After OS restart starting Colima al is gone, docker ps-a is empty, the created volumes are also gone. Using...

As a workaround I have adjusted srsservice_deployment.yaml, with a custom volume mount based on a secret containing the cacerts with the added ca's: ``` volumeMounts: - mountPath: /etc/ssl/certs/java/ name: cacerts...

Hi @bhowd1 , Its not about certificates for authentication, its about CA certificate for the initial TLS handshake. We are using regular authentication (username & password). The company is using...

> @dekke046 @bhowd1 I've deployed SRS in a similar environment, and the configuration is a bit counterintuitive for this scenario. The issue is that if you have srsStorage.tls.enabled set to...

@sobomax Is the above possible at all?

@kishorv10 @konire , Can you please have a look how to incoporate this on a global level for each chart? So not only for the backingservices, but also for pega...

@konire @kishorv10 @reddy-srinivas @ravitejamekapega, Perhaps this can be looked at more generic. I am facing customisations to the template files due to company security settings and therefore for all containers/pods...

@kishorv10 At least I had to make securityContext changes to the following files for the Pega chart: ``` ./charts/pegasearch/templates/pega-search-deployment.yaml ./templates/_pega-deployment.tpl ./templates/_helpers.tpl ``` For the backingservices: `./charts/srs/templates/srsservice_deployment.yaml` I have not checked...