2025.09 (September 2025)

Update CAS Servers

This version contains an update to CAS. However, until the existing CAS servers are restarted, your deployment continues to run the earlier version.

Although you must delete the CAS server pods in order to restart CAS and complete your update, note the following caveats:

• Deleting the CAS server pods stops the running CAS servers, drops all the in-memory data, and restarts the new pods.
• The updated CAS servers might need to be reloaded with data.
• Stopping and starting the CAS servers cause an outage that will be noticeable for the end users. Make plans accordingly.

After you have performed the commands to deploy the updates, you must delete the existing CAS pods, which will restart an updated CAS server. As an administrator with namespace privileges, run the following command:

kubectl -n name-of-namespace delete pods -l app.kubernetes.io/managed-by=sas-cas-operator

Removal of Support for Kaniko

Support for Kaniko has been removed from SAS Decisions Runtime Builder, finishing the process begun in the 2025.06 release (see BuildKit Replaces Kaniko as Default for Container Images for more information). If you continued to use Kaniko with the SAS Decisions Runtime Builder service after the 2025.06 update, or if you were directed to skip the deployment note at 2025.06 because you are updating through several releases at once, references to Kaniko must be removed from the base kustomization.yaml file.

• Search for - site-config/sas-decisions-runtime-builder/kaniko in the resources block. If it is present, remove it.
• Search for - sas-bases/overlays/sas-decisions-runtime-builder/kaniko/kaniko-transformer.yaml in the transformers block. If it is present, remove it.
• Search for - sas-bases/overlays/sas-decisions-runtime-builder/buildkit/buildkit-kaniko-transformer.yaml in the transformers block. If it is present, replace it with - sas-bases/overlays/sas-decisions-runtime-builder/buildkit/buildkit-transformer.yaml.

New Configuration File Format

The configuration files for controlling the size of the persistent volume claim (PVC) used by the SAS Model Publish service have been revised. The new format will simplify future updates.

1. In the resources block of the base kustomization.yaml file ($deploy/kustomization.yaml), search for the following line:
   - site-config/sas-model-publish/git

   - site-config/sas-model-publish/git

   If the line is not present, you are not affected by the change and should skip the rest of the deployment note. If the line is present, continue with Step 2.

2. To use the new configuration files, follow the steps described in the README file at $deploy/sas-bases/examples/sas-model-publish/git/README.md (for Markdown format) or at $deploy/sas-bases/docs/configure_git_for_sas_model_publish_service.htm (for HTML format).
   Note: SAS recommends referring to the $deploy/site-config/sas-model-publish/git/storage.yaml file while updating the new configuration.env file to ensure that the values used in your current deployment are used in the update.
3. The new configuration of the files means that the properties and values used in the old storage.yaml file are now in the configuration.env file. Because the file is no longer needed, delete $deploy/site-config/sas-model-publish/git/storage.yaml from your deployment assets.

Remove Kaniko References

If you continued to use Kaniko with the SAS Model Publish service after the 2025.06 update, remove references to it from the base kustomization.yaml file. Take the following steps:

1. Search for - site-config/sas-model-publish/kaniko in the resources block. If it is present, remove it.
2. Search for - sas-bases/overlays/sas-model-publish/kaniko/kaniko-transformer.yaml in the transformers block. If it is present, remove it.
3. Delete the $deploy/site-config/sas-model-publish/kaniko directory from your deployment assets.