Deploying your custom HCL Commerce Version 9.1 Helm Chart to your cloud infrastructure

Once you are satisfied with the HCL Commerce deployment that you customized within the SoFy sandbox, you can deploy it to the production cloud infrastructure of your choice.

This is done by using Helm on your own Kubernetes cloud platform.

Before deployment, refer to the SoFy Guides page for instructions to install the required solutions on your own Kubernetes cluster. There you will learn how to set your own domain and configure the necessary SSL certificates that are required to deploy from SoFy.

Important: The environment that you create should not be used for a live production site without further consideration toward security hardening, load balancing, ingress routing, and performance tuning. To operate HCL Commerce Version 9.1 in a live production environment, you must commit further time and resources to both performance and security considerations.

With load balancing and ingress routing specifically, you can configure which services you want to expose externally, and restrict the remaining services within the cluster network. This configuration limits their access from and exposure to the wider Internet.

Procedure

For the generated HCL Commerce Helm Chart configuration, you must specify the following parameters when you deploy on your own Kubernetes cluster.
Parameter Description

global.hclImagePullSecret The secret containing your credentials to the HCL Docker Repository.

For example, you can use a Helm command similar to the following to deploy your HCL Commerce SoFy solution Helm Chart on your Kubernetes cluster.
```
helm upgrade --install RELEASE_NAME CHART_LOCATION -n NAME_SPACE \
    --set global.hclImageRegistry="IMAGE_REGISTRY" \ 
    --set global.hclImagePullSecret="IMAGE_PULL_SECRET \
```
Optional: Disable Tooling analytics.
Management Center for HCL Commerce in all releases 9.1.12.0 and greater now report business user analytics to HCL. This information assists HCL in the development of new features and the enhancement of existing business user tools.
To disable Tooling analytics:
- If you use Vault in your deployment, set the Vault allowTelemetry key value to no prior to deployment.
- Set the Tooling Web Docker container ALLOW_TELEMETRY container environment variable to no on deployment.