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
123 stars 194 forks source link

Image failed to pull from the Repo "Hazelcast by using “clusteringServiceImage" #559

Open wreddybeem opened 1 year ago

wreddybeem commented 1 year ago

Hello Team, When we are trying to deploy the Hazelcast by using “clusteringServiceImage”, It is failing with the below errors. We tried Configurations which are instructed in document, but the result is same error:

https://github.com/pegasystems/pega-helm-charts/tree/master/charts/pega/charts/hazelcast

Error: Failed to pull image "wfcertifiedvirtual.wfcr.wellsfargo.net/prmilm-aksilmpoc:1.3.2-11": rpc error: code = Unknown desc = failed to pull and unpack image "wfcertifiedvirtual.wfcr.wellsfargo.net/prmilm-aksilmpoc:1.3.2-11": failed to resolve reference "wfcertifiedvirtual.wfcr.wellsfargo.net/prmilm-aksilmpoc:1.3.2-11": failed to authorize: failed to fetch anonymous token: unexpected status: 401

This same repo connectivity successfully in pulling the Image with the below configuration with Tag as below: Please see the attachments and fix the authentication issue

hazelcast configurations hazelcast configurations1

MadhuriArugula commented 1 year ago

@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 authentication. Please check if you have provided right details.

Also as mentioned in the documentation part of values.yaml, if platform version is greater than or equal to 8.8, use clusteringServiceImage, else image in the sub chart configuration

kishorv10 commented 4 months ago

@wreddybeem Is the issue resolved? Can you update the latest status?