Walkthrough: Adding the SFCRM connector module to Sitecore in Azure Kubernetes Service

Version: 8.0

You can add the Sitecore Connect for Salesforce CRM (SFCRM) connector to a Sitecore container environment in Azure Kubernetes Service (AKS).

This walkthrough describes how to:

Build images and push them to Azure

To build the images for SFCRM and push them to Azure:

Build the images for SFCRM as explained in Walkthrough: Preparing to install the SFCRM connector in a container environment.

Note

The Kubernetes deployment requires an mssql-init image. You must ensure that you include mssql-init in your docker-compose-override.yml file.

Open the Windows console, and use the docker tag command to tag the images. For example:

RequestResponse

docker tag sitecore-sfcrm-xp1-cm:10.1.0.005207.643-10.0.17763.1757-ltsc2019 $registry/sitecore-sfcrm-xp1-cm:<tag version>

In the console, use the docker push command to push the images to your Azure registry. For example:
RequestResponse
```
docker push $registry/sitecore-sfcrm-xp1-cm:<tag version>
```

To prepare files and folders in your installation for deployment:

Download the Sitecore SFCRM container deployment package from the Sitecore download page and extract it to a folder on your local workstation.
Open the folder that you extracted the Sitecore SFCRM container deployment package to.
Navigate to the k8s\<version>\<topology> folder, for example, k8s\ltsc2019\xp1. Copy the overrides subfolder to the Sitecore Experience Platform (SXP) container deployment package folder k8s\<version> (on the same level as the xp1 folder).
In the SXP container deployment package, in each of the overrides, overrides\xp1\init, and overrides\xp1\secrets folders, locate the kustomization.yaml file. In each file, update the bases parameter with the appropriate folder names for your installation, for example, ../../xp1.

Note

The bases parameter contains the placement of the original Sitecore container deployment files that the kustomization.yaml files override.
In each of the kustomization.yaml files, in the images: section, update the newName and newTag parameters with the values for the mssql-init, cm, xdbcollection, xdbsearch and xdbsearchworker images you pushed to the Azure Registry.
In the overrides\xp1\secrets folder, in the sitecore-salesforce-crm-connection-string.txt file , replace the content with the connection string you prepared in ???.

To deploy the containers and the necessary Kubernetes components:

Prepare the AKS cluster configuration and deploy the ingress controller. For information on how to do this, see the Installation Guide for Production Environment for Kubernetes, which is available on the Sitecore download page.
Open the Windows console, and navigate to the folder containing the xp1 and overrides folders.
Deploy the secrets. Use this command:
RequestResponse
```
kubectl apply -k ./overrides/xp1/secrets/
```
Run the external folder. Use this command:
RequestResponse
```
kubectl apply -k ./xp1/external/
```
Wait for all containers to have the status Ok/Running. You can check the status with this command:
RequestResponse
```
kubectl get pods -o wide
```
Run the init folder. Use this command:
RequestResponse
```
kubectl apply -k ./overrides/xp1/init/
```
Wait for all containers to have the status Completed. You can check the status with this command:
RequestResponse
```
kubectl get pods
```
To create persistent volumes, run this command:
RequestResponse
```
kubectl apply -f ./xp1/volumes/azurefile
```
Run the Sitecore containers with the SFCRM changes. Use this command:
RequestResponse
```
kubectl apply -k ./overrides/xp1/
```
Wait for all containers to have the status Ok/Running. You can check the status with the kubectl get pods command.
Update the local host file. For information on how to do this, see the Installation Guide for Production Environment for Kubernetes, which is available on the Sitecore download page.
Update your search indexes.

Do you have some feedback for us?

If you have suggestions for improving this article,