Alauda Container Platform
  • English

    • Upgrade

    INFO

    This document provides the upgrade path principles and supported version compatibility for Alauda Container Platform Compliance for Kyverno.

    NOTE

    Starting in ACP 4.5, Alauda Container Platform Compliance for Kyverno is named Alauda Container Platform Policy Management. Search for Alauda Container Platform Policy Management when you download the plugin from the Customer Portal. A plugin package published before the rename still shows Alauda Container Platform Compliance for Kyverno in the platform after you upload it.

    TOC

    Compatibility MatrixUpgrade Path GuidelinesUpgrade Alongside ACPMinor Version UpgradePatch-Level Upgrade

    Compatibility Matrix

    The table below lists supported versions of the Alauda Container Platform Policy Management (previously Alauda Container Platform Compliance for Kyverno):

    Compliance for Kyverno VersionSupported Alauda Container Platform Version
    4.3.x4.2.x, 4.3.x
    4.2.x4.2.x

    Upgrade Path Guidelines

    Upgrade Alongside ACP

    • Description: In ACP 4.1.x and earlier releases, Policy Management (previously Compliance for Kyverno) plugins were lifecycle-aligned with ACP and were upgraded as part of the ACP release. For the following upgrade paths, the plugins are upgraded alongside ACP to version 4.3.0 during the ACP upgrade process.
    • Supported ACP Upgrade Paths:
      • 4.0.x -> 4.3.0
      • 4.1.x -> 4.3.0
    • Result: After the upgrade is completed, all Policy Management (previously Compliance for Kyverno) plugins are upgraded to version 4.3.0.

    Minor Version Upgrade

    • Description: Policy Management (previously Compliance for Kyverno) plugins support minor version upgrades when ACP is on a compatible version.
    • Prerequisite: ACP version must satisfy the compatibility matrix above.
    • Example: 4.2.x -> 4.3.x

    Patch-Level Upgrade

    • Description: Upgrades between any patch versions within the same minor version are fully compatible and can be performed directly.
    • Example: 4.3.0 -> 4.3.x