Updating Managed Cloud Containers
As part of your Managed Cloud Containers solution you can update the services in your environment using the Update images pipeline when an update has been made to image references for known Sitecore application services. If a custom service is provided for you with a new image reference, that service will also be added and made available as part of the update options for the pipeline run.
To run the Update images pipeline, the images being updated must already be in the Azure Container Registry (ACR) that is created as part of your Managed Cloud Premium container solution.
You can update multiple Sitecore image references within the same pipeline run.
For the Update images pipeline, you must:
-
Run from the
mainbranch only. -
Provide a path with the following format:
{ACR name}.azure.io/{image name}:{image tag}. -
Use
NAby default for Sitecore image references where the update is not needed.
Update pipeline configuration
The Update pipeline configuration dialog lets you:
-
Use predefined fields for Sitecore application images, such as CM, CD, ID, and PRC, depending on the selected topology (XP or XM), which only require a path parameter.
Pipeline run process
The Update pipeline completes the run process as follows:
-
When you set the applicable image references, the pipeline validates whether the images are in the ACR.
NoteIf the path is invalid the pipeline validation will fail and will present the error message for evaluation.
-
If they are available, the pipeline updates the corresponding images in the configuration file through a Pull Request (PR), which is created and completed automatically.
-
As a result of the pipeline, the application pipeline is triggered and rolls out the images to the customer Kubernetes cluster.