How to upgrade Sitecore Managed Cloud Containers solutions to AKS 1.33


Description

The end of life of Azure Kubernetes Service (AKS) 1.32 is March 2026. Sitecore Managed Cloud Containers solutions based on AKS 1.32 must be updated to a newer version that uses AKS 1.33. For more details on AKS's end of life and the consequences of deprecation, refer to Microsoft's FAQ.

The following article contains upgrade instructions for the Sitecore Managed Cloud Containers solution to the version that uses AKS 1.33.

Breaking Changes

Sitecore 10.1.x support is stopped as Windows 2019 node pools used in that version, are deprecated.

Upgrade Instructions

  1. Download an upgrade package for the needed topology and version from the storage. There is a list of available upgrade packages:
    • Sitecore 10.2.0:
      • mcc.xp.upgrade.10.2.0-r.0.1.575391.nupkg
      • mcc.xm.upgrade.10.2.0-r.0.1.575391.nupkg
    • Sitecore 10.2.1:
      • mcc.xp.upgrade.10.2.1-r.0.1.575392.nupkg
      • o mcc.xm.upgrade.10.2.1-r.0.1.575392.nupkg
    • Sitecore 10.2.2:
      • mcc.xp.upgrade.10.2.2-r.0.1.575393.nupkg
      • mcc.xm.upgrade.10.2.2-r.0.1.575393.nupkg
    • Sitecore 10.3.0:
      • mcc.xp.upgrade.10.3.0-r.0.1.575394.nupkg
      • mcc.xm.upgrade.10.3.0-r.0.1.575394.nupkg
    • Sitecore 10.3.1:
      • mcc.xp.upgrade.10.3.1-r.0.1.575395.nupkg
      • mcc.xm.upgrade.10.3.1-r.0.1.575395.nupkg
    • Sitecore 10.3.2:
      • mcc.xp.upgrade.10.3.2-r.0.1.575397.nupkg
      • mcc.xm.upgrade.10.3.2-r.0.1.575397.nupkg
    • Sitecore 10.3.3:
      • mcc.xp.upgrade.10.3.3-r.0.1.575398.nupkg
      • mcc.xm.upgrade.10.3.3-r.0.1.575398.nupkg
    • Sitecore 10.4.0:
      • mcc.xp.upgrade.10.4.0-r.0.1.575399.nupkg
      • mcc.xm.upgrade.10.4.0-r.0.1.575399.nupkg
    • Sitecore 10.4.1:
      • mcc.xp.upgrade.10.4.1-r.0.1.577550.nupkg
      • mcc.xm.upgrade.10.4.1-r.0.1.577550.nupkg
  2. Install the upgrade package to your solution (follow the guideline for Sitecore 10.2)
  3. After merging changes to Infrastructure repo,
    • If the environment does not have DR installed, run the Infrastructure pipeline.
    • If the environment uses DR Managed Hot, run the Infrastructure pipeline with Synchronize primary to secondary checked.
    • If the environment uses DR Basic Cold Standby,  run the Infrastructure pipeline with Update outage app checked.
  4. After merging changes to Application repo, run the Application pipeline.
  5. Run the check cluster upgrades pipeline.
  6. Run the cluster version upgrade pipeline (Kubernetes_version 1.33.0).
  7. If the environment uses DR Managed Hot, complete the following,
    • Run the dr cluster version upgrade pipeline (Kubernetes_version 1.33.0).