What's Changed
This release includes an upgrade to the image base for Assemblyline to move from:
Debian Bookworm with Python 3.11 → Debian Trixie with Python 3.14.
This is going to be considered an important minor bump as this can impact service builds with the change to the Python interpreter and can break Scaler's interaction with the Kubernetes API as mentioned in this issue.
IMPORTANT FOR KUBERNETES DEPLOYMENTS: Clusters that were originally created on Kubernetes v1.16 or earlier have a root CA certificate without the Subject Key Identifier (SKID) and Authority Key Identifier (AKI) extensions. In newer versions of the urllib3 (such as what's included in this release), requests will fail with a CERTIFICATE_VERIFY_FAILED/Missing Authority Key Identifier error.
We recommend to rotate your cluster's CAs before deploying this version as failure to do so will cause the scaling component of Assemblyline to crash.
Supporting References:
- Amazon: https://docs.aws.amazon.com/eks/latest/userguide/certificate-authority-rotation.html
- Azure: https://learn.microsoft.com/en-us/azure/aks/rotate-certificates#manually-rotate-cluster-ca-certificates
- Google: https://docs.cloud.google.com/kubernetes-engine/docs/how-to/credential-rotation
- Rancher: https://ranchermanager.docs.rancher.com/how-to-guides/new-user-guides/manage-clusters/rotate-certificates
IMPORTANT FOR SERVICE DEVELOPERS: Before creating a new build, you may want to either:
- Verify the service code and dependencies are compatible with Python 3.14 if you want to continue to use the
stableorlatesttags for the service-base - Change the image tag used as the base in your Dockerfile to point to a versioned alias (ie.
4.8.stableor4.8.latest)
In either case, we would expect the versions of your service to match the base that you're using to build with to assess compatibility.
If you have any questions or require support, feel free to reach out to us on Discord.