search

pegasystems / pega-helm-charts

Orchestrate a Pega Platform™ deployment by using Docker, Kubernetes, and Helm to take advantage of Pega Platform Cloud Choice flexibility.
https://community.pega.com/knowledgebase/articles/cloud-choice
Apache License 2.0
122 stars 195 forks source link

Azure Keyvalut secrets config are not working in Pega systems #599

Open vvinothkumar1 opened 12 months ago

vvinothkumar1 commented 12 months ago

Is your feature request related to a problem? Please describe. Presently we are not able to create Azure keyvalut secrets and make Pega AKS run with AKS secrets, presently we are using Kubernetes Secrets only.

Describe the solution you'd like Like to use AKS secrets instead of Kubernetes secrets.

Describe alternatives you've considered presently using Kubernetes secrets.

Additional context Please have document here or send us if you already have that facliities to configure secrets in AKS so Pega can use from AKS server instead of using from Kubernetes secrets.

arvasrikanth commented 11 months ago

@vvinothkumar1 Pega already supports external secret feature to store credentials and other sensitive information. Can you check documentation here.

mxchinegod commented 11 months ago

@vvinothkumar1 Pega already supports external secret feature to store credentials and other sensitive information. Can you check documentation here.

What is expected behavior? We have a secret.yaml file in templates/ dir of the chart and have declared its name in external_secret_name and yet Pega creates a secret and prepends onto it the name we have given for external_secret_name...?

Screenshot 2023-08-03 at 10 01 45 AM Screenshot 2023-08-03 at 10 03 17 AM Screenshot 2023-08-03 at 10 03 27 AM

This is not created by us nor do we wish to use it yet it is being made and contains no useful information for deployment thus Tomcat FAILURE on context.xml read attempt since context.xml.tmpl is generated using these templated values.

Please advise, this behavior seems odd.

kishorv10 commented 2 months ago

Hi, @mxchinegod Can you please try it again? We have made a few changes to the secrets created as part of #632. This would remove the duplicate secret creation. Please try the deployment on the latest chart version. Revert to us in case of any issues.

github-actions[bot] commented 2 weeks ago

This issue has been marked as stale because it has been open for 60 days with no activity. This issue will be automatically closed in 30 days if no further activity occurs.