In this section, we will collect and describe API changes (or other breaking changes), describe the migration process and suggest backwards compatibility options for upgrades from earlier versions.

Note: Always check this page before upgrading to a new major/minor release.

helm rollback does not work with the KAI Scheduler chart. The chart uses Helm lookup guards and .Release.IsInstall conditionals to create resources (namespaces, queues, service accounts) only when they don't already exist. At install time these resources are rendered into the stored manifest. On rollback, Helm replays the stored manifest verbatim and fails when the resources already exist in the cluster.

To downgrade, use uninstall + reinstall instead:

helm uninstall kai-scheduler -n kai-scheduler
helm install kai-scheduler oci://ghcr.io/nvidia/kai-scheduler/kai-scheduler \
  --version <TARGET_VERSION> -n kai-scheduler

All queues, workloads, CRDs, and PodGroups are preserved across this cycle. See the v0.13.0 Migration Guide for full details.

1. Verify whether your upgrade path traverses any versions impacted by a breaking change.
2. Click through to the version-specific folder.
3. Follow the “What Changed,” “Impact,” or “Rollback / Pin to Legacy Settings” instructions.
4. If you need help, refer to our issue template.