The end of life of Azure Kubernetes Service (AKS) 1.28 is November 2024. Sitecore Managed Cloud Containers solutions, based on AKS 1.28, need to be updated to a newer version that uses AKS 1.29. For more details on AKS end of life and the consequences of deprecation refer to here.
This article contains upgrade instructions for the Sitecore Managed Cloud Containers solution to the version that uses AKS 1.29.
There are no breaking changes in this release.
For all versions, downtime will be encountered during the upgrade process. The upgrading process for Sitecore Managed Cloud Containers should be performed as described below.
Follow the below steps to upgrade the Sitecore Managed Cloud Containers solution to the version that uses AKS 1.29:
- Download an upgrade package for the required topology and version from the storage. Here is the list of the available upgrade packages:
- Sitecore 10.1.0:
- mcc.xp.upgrade.10.1.0-r.0.1.394606.nupkg
- mcc.xm.upgrade.10.1.0-r.0.1.394606.nupkg
- Sitecore 10.1.1:
- mcc.xp.upgrade.10.1.1-r.0.1.394607.nupkg
- mcc.xm.upgrade.10.1.1-r.0.1.394607.nupkg
- Sitecore 10.1.2:
- mcc.xp.upgrade.10.1.2-r.0.1.394608.nupkg
- mcc.xm.upgrade.10.1.2-r.0.1.394608.nupkg
- Sitecore 10.1.3:
- mcc.xp.upgrade.10.1.3-r.0.1.394609.nupkg
- mcc.xm.upgrade.10.1.3-r.0.1.394609.nupkg
- Sitecore 10.2.0:
- mcc.xp.upgrade.10.2.0-r.0.1.394610.nupkg
- mcc.xm.upgrade.10.2.0-r.0.1.394610.nupkg
- Sitecore 10.2.1:
- mcc.xp.upgrade.10.2.1-r.0.1.394611.nupkg
- mcc.xm.upgrade.10.2.1-r.0.1.394611.nupkg
- Sitecore 10.3.0:
- mcc.xp.upgrade.10.3.0-r.0.1.394612.nupkg
- mcc.xm.upgrade.10.3.0-r.0.1.394612.nupkg
- Sitecore 10.3.1:
- mcc.xp.upgrade.10.3.1-r.0.1.394613.nupkg
- mcc.xm.upgrade.10.3.1-r.0.1.394613.nupkg
- Sitecore 10.4.0 (new release): not available.
- Install the upgrade package to your solution (follow the guidelines for Sitecore 10.1 or Sitecore 10.2, or Sitecore 10.3).
- After merging changes to Infrastructure repo, run the Infrastructure pipeline.
- After merging changes to Application repo, run the Application pipeline.
- Run the check cluster upgrades pipeline.
- If the environment uses DR Managed Hot Standby, do the following:
Run the infrastructure pipeline with Synchronize primary to secondary checked.
- If the environment uses DR Cold Standby, do the following:
Run the infrastructure pipeline with Update outage app checked.
- Run the cluster version upgrade pipeline (Kubernetes_version 1.29.4 - select the latest available patch version received from the pipeline in the previous step).
- If the environment uses DR Managed Hot:
- Run the dr cluster version upgrade pipeline (Kubernetes_version 1.29.4 - select the latest available patch version received from the pipeline in step 4).