MadhuriArugula

@ragsns Can we close this PR as it is duplicate of #236

@je-munobia You caught that right. It is an issue with the recent changes in the installer chart. Thanks for reporting the issue. It wasn't intentional to have only `post-install` hook....

@je-munobia We have fixed the issue with ```waitForJobCompletion``` in recent PR's and the change is already in master. You should be receiving the fix in newer helm release which will...

> @MadhuriArugula Great - that was fast! > I took a look at master and noted that https://github.com/pegasystems/pega-helm-charts/blob/master/charts/pega/charts/installer/templates/_pega-installer-job.tpl#L11 might need to be changed to: > `"helm.sh/hook": post-install,post-upgrade` @je-munobia We already...

The issue has been addressed as part of #312 available from helm chart version v1.6.2

@raghavf1 Can you update the PR with an explanation of the change and that it will not impact backwards compatibility? Also you might want to fix the unit tests failed...

@rohit-eaisystems I'm assuming you have performed Pega 8.4.1 Install through helm ( with command `helm install .`. If yes, then you already have helm release `` to which resources are...

Closing the issue with the above provided explanation.

@wreddybeem Error shared doesn't seem to be specific to the screenshots shared. `"wfcertifiedvirtual.wfcr.wellsfargo.net/prmilm-aksilmpoc:1.3.2-11": failed to authorize: failed to fetch anonymous token: unexpected status: 401` clearly is an issue with registry...

@micgoe I would like to understand your use case for not specifying the CPU limits for the deployment as keeping CPU limits open may consume all the resources on the...