maracle6

This would also be useful for pega tiers, for Stream or in case any other volume claim is required for some reason.

@momchilgochev Please check if release 3.13.0 resolves your issue (srsruntime.imagePullSecretNames)

Please add a customerDeploymentID to the global section of your values file. For example: ``` --- global: # This values.yaml file is an example. For more information about # each...

@mefrom This functionality is now available in release [v3.13.0](https://github.com/pegasystems/pega-helm-charts/tree/v3.13.0) or later

You should be able to configure it using the storageClassName element. https://github.com/pegasystems/pega-helm-charts/blob/28937d96ebb2383fd5e57b9f6d3e727b3e3177d9/charts/pega/values.yaml#L29

> @dcasavant is this enhancement still needed? It's been open for quite a while, so there doesn't seem to be much urgency. This is already available, by setting custom.env.CONTEXT_XML_SNIPPET. It's...

I don't think so, but I haven't use the install image in quite a while

@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 false...