The Managed Cloud pipelines

Abstract

Describes the pipelines that are involved with Managed Cloud for containers.

Each Sitecore Managed Cloud client has the following pipelines to control their solution: Application, Infrastructure, Frontdoor, Pod restart, Node restart, Windows node upgrade, and Sitecore license update, Cluster upgrades, Cluster version upgrades. You can modify the existing pipelines or add your own.

You use the Application pipeline to deliver application code. It deploys Ansible scripts to set up the Azure Kubernetes Service (AKS) pods containing each running container. You must use the Application repository to customize your Sitecore solution and to customize your Managed Cloud instance. You must build customized containers with your application elements, upload them to the Azure Container Registry (ACR), and change references to use your new customized images..

You can trigger the pipeline automatically and manually.

You use the Infrastructure pipeline to deliver infrastructure code. It deploys Terraform scripts to read the configuration and synchronize all elements of the deployment to match the settings in the configuration files. After the pipeline has run successfully, the Infrastructure Terraform state file is stored in an Azure Storage account.

You can trigger the pipeline automatically and manually.

You use the Frontdoor pipeline to deploy Terraform scripts to read the configuration and synchronize all elements of the deployment to match the settings in the configuration files. When the pipeline has run successfully, the Frontdoor Terraform state file is stored in an Azure Storage account. After the Frontdoor configuration is updated, you must trigger the Frontdoor pipeline manually .

You use the Pod restart pipeline to restart the Sitecore solution without downtime. For example, you can use it to get your app working again if your container reports an error and the Kubernetes (k8s) can not handle it.

To restart a specific deployment, run the pipeline and choose the target deployment:

MCC-pod_restart.png

You use the Node restart pipeline to restart Kubernetes nodes, for example, to complete an operating system update. The pipeline has two options: restart Windows or/and Linux node types.

You can choose a type of scale set to restart (Windows or Linux) and trigger a pipeline.

Note

All nodes for a target node type are restarted simultaneously and you must expect downtime for about 5 minutes.

MCC-node_reboot.png

Note

If you extended your solution with a Kubernetes deployment (for a Sitecore module or another service), the Node reboot pipeline may fail because of a Kubernetes deployment restart timeout. To mitigate this issue, you must extend the progressDeadlineSeconds value.

You use the Windows node upgrade pipeline to upgrade the AKS Windows node pool OS image. For more information, see the Microsoft Azure documentation. You can check upgrade availability using Azure CLI.

You use the Sitecore license update pipeline to upgrade the Sitecore license for the existing deployment. To update the license, you must copy the Sitecore license content and paste it into the Azure devops parameter field while running the pipeline. The license is updated without downtime.

It is important to regularly use the Cluster upgrades pipeline to check which Kubernetes releases are available for your cluster. This makes sure that you have the latest version of AKS including new features and bugfixes. For more information, please refer to the Microsoft documentation.

You use the Cluster version upgrade pipeline to upgrade the AKS cluster. This pipeline runs with no downtime.

The pipeline upgrades the following to the newer versions:

  • The control panel.

  • The Linux node pool.

  • The Windows node pool.

Note

If the pipeline fails, contact Sitecore Support to resolve the issue.