4.1 Release Notes:
- Assemblyline will be more restrictive in terms of what service versions are allowed to run because of platform incompatibility (ie. a service on 4.1 may not necessarily work on a 4.0 system)
This means if you upgrade the system to 4.1 before your services have been built for 4.1, Assemblyline will start to disable those services until an update comes in with a matching '4.1' prefix. - System will be overall more responsive to changes made to the UI with thanks to using events rather than polling to drive core actions.
- Service Base & Dependencies:
- Persistent Service Updaters: updaters will now run as Deployments rather than Jobs in Kubernetes. This entails a change in updater code for existing services under 4.0 where this would now be considered a dependency container. See the docs for more information.
- Sync Interval: There is now pre-defined buckets for setting the sync interval in the UI. You will still have the option of setting the sync interval at a granular level as in 4.0.
- Ingestion: You're now able to increase the number of ingest, complete, and submit threads in Ingester by setting the corresponding environment variables. This can be done by using coreEnv in the values.yaml when deploying.
- Updater: Improved support for Harbor registries as well as for insecure local registries (ie. for development)
- Helm:
- Storage: ReadWriteMany (RWX) is no longer a requirement
- Unified tags for releases:
4.0: You have to set the tag version for core, ui, frontend, and service-server (if defaults aren't taken)
4.1: You will only need to set one tag version that will apply to all components