A conflict might occur between the supported SAS Viya Long-Term Support update path and the Kubernetes versions available from their Kubernetes provider.
When updating from one SAS Viya LTS release to a later LTS release, you must apply all intermediate LTS releases shown in the documented in sequence. Skipping a Long-Term Support release is not supported.
For example, the supported update path from SAS® Viya® LTS 2024.09 to SAS® Viya® LTS 2026.03 is as follows:
Therefore, the following direct updates are not supported:
This issue might occur when the Kubernetes provider does not make the Kubernetes versions required by the intermediate SAS Viya releases available. For example, the provider might allow Kubernetes to be upgraded directly from version 1.30 to version 1.34 without offering an intermediate version.
The following conditions might apply:
In the example path from LTS 2024.09 to LTS 2026.03, the published compatibility table identifies the following Kubernetes version ranges:
These version ranges are examples based on the published compatibility table when this article was written. Always check the current documentation before planning an update because the supported versions can change.
IMPORTANT: Your SAS Viya deployment must run on a supported Kubernetes version. Before updating SAS Viya or Kubernetes, verify compatibility for the following:
When upgrading Kubernetes, carefully review the Kubernetes provider’s documentation for supported versions, version life cycle information, and any breaking changes introduced by the provider or another third party.
SAS Viya LTS releases contain documented update paths. Intermediate LTS releases can contain required deployment changes that must be completed before updating to a later LTS release.
SAS documentation states that the updates must be completed in the documented order and that skipping a Long-Term Support release is not supported. Each update in the sequence must be completed, including all applicable deployment notes. For additional information, see SAS Viya Platform Operations: Versions in Standard Support and Update Paths.
The supported SAS Viya update path assumes that the prerequisites for every target release are met. These prerequisites include the following:
The availability or life cycle of Kubernetes versions from a third-party provider does not change the documented SAS Viya update sequence.
The following actions do not create a supported SAS Viya update path:
See SAS Viya Platform Operations: Versions in Standard Support and Update Paths to identify the supported update sequence.
For example, you would complete the following documented path in order:
SAS Viya LTS 2024.09 ► SAS Viya LTS 2025.03 ► SAS Viya LTS 2025.09 ► SAS Viya LTS 2026.03
For each target release, complete the following steps:
Note: Do not skip SAS Viya LTS 2025.03 or SAS Viya LTS 2025.09 when updating from SAS Viya LTS 2024.09 to SAS Viya LTS 2026.03.
See SAS Viya Kubernetes Version Support for the current compatibility table.
Do not assume that a Kubernetes version supported by the final SAS Viya release is also supported by the current or intermediate SAS Viya releases.
Plan the SAS Viya and Kubernetes changes together so that the deployment remains on a supported combination at every stage.
At every stage, verify the following:
There is no universal rule to always update Kubernetes first or SAS Viya first. The order depends on the compatibility overlap between the currently deployed SAS Viya release and the next SAS Viya target release.
If the available Kubernetes versions do not permit a supported transition, do not proceed with the proposed in-place sequence.
For Microsoft Azure Kubernetes Service, review Supported Kubernetes versions in Azure Kubernetes Service (AKS).
Microsoft documents AKS version availability, support timelines, and Long Term Support options.
If a Kubernetes version required for an intermediate SAS Viya update is no longer available under standard AKS support, complete the following steps:
AKS LTS does not change or replace the SAS Viya update sequence. It might provide additional Kubernetes life cycle coverage that enables the documented SAS Viya update path.
If the proposed path skips an intermediate SAS Viya LTS release, do not proceed with that path.
SAS Technical Support cannot provide the following for an unsupported direct update:
This situation is not a documentation gap when the documentation explicitly identifies the supported update sequence and states that skipping an LTS release is not supported.
If the Kubernetes provider cannot provide a version compatible with the required in-place update stages, you might need to evaluate an alternative deployment and migration strategy.
A new deployment and migration is separate from an in-place update. Do not assume that a SAS Viya platform backup recreates the complete Kubernetes environment.
The evaluation should include the following:
Complex deployments and solution-specific workloads might require engagement with the appropriate SAS services or consulting team.
A fresh installation and restore should not be presented as an automatic replacement for the supported in-place update path until you review the migration requirements for the complete environment.
Before completing each supported update, create and validate the required backups.
Review and protect the following items (when applicable):
A SAS Viya backup does not include every Kubernetes resource, external data source, file system, or persistent volume. Review the documented backup scope and protect excluded items separately.
See Backup and Restore: Overview for additional information.
Rehearse the complete SAS Viya and Kubernetes update sequence in a representative non-production environment before updating Production.
Include the following areas in the validation plan (when applicable):
Note: Review the deployment notes for every release in the sequence, not only the final target release.
See the following resources when planning the update:
Review these resources again immediately before the planned update because SAS Viya releases, supported update paths, and Kubernetes compatibility information can change.
No. Follow the documented sequence through SAS Viya LTS 2025.03 and SAS Viya LTS 2025.09.
No. You cannot skip SAS Viya LTS 2025.09.
No. The Kubernetes provider’s version availability does not change the documented SAS Viya update sequence.
Only when the currently deployed SAS Viya release supports that Kubernetes version. Otherwise, the resulting combination is unsupported.
No. It is a separate migration approach that requires a complete assessment of the SAS Viya platform, licensed solutions, configuration, content, and external dependencies.
No. Review the documented backup scope and separately protect content that is not included in the SAS Viya backup.
Microsoft documents AKS LTS as an option for extended support for eligible Kubernetes versions. Confirm eligibility and version availability with the Azure administrator or Microsoft. AKS LTS does not remove the requirement to complete the documented SAS Viya update sequence.