Troubleshooting

If issues arise during the configuration or deployment process, you could try to execute the following steps for testing your deployment.

Correct CORS Configuration

Ensure the hr-customer-profile-service-patch.yaml file has the correct allowOrigin values under the cors settings. An example of a correct configuration is as follows: 
 values:  cors:  allowOrigin:  - ${C4R_BASE_URL}  - https://qa-gkr.cloud4retail.co

Ensure that the allowOrigin URLs are correctly specified and accessible.

Note:
Please ensure URL for allowsOrigin is depended on the target cloud environment at must be set in cooperation with the install team or the DevOps

Check Logs or Send a Request

You could try making a request to the CPS API from a domain specified in the allowOrigin settings. Ensure that the API responds without CORS errors.

Use Helm and Kustomize logs to identify any issues during the deployment.

Use kubectl to inspect the logs of the service pods.

Note:

Reach out to the DevOps team responsible for creating the cloud environment and request the possible internal URL variants that can be used for Employee Hub access. For example, we currently had to add:

  • https://qa.cloud4retail.co
  • https://qa.cloud4retail.com