If you want to migrate to LTS 10.0 and run the Axon Ivy Engine in a container environment such as Kubernetes, you may have made configurations such as the ivy.yaml accessible to the Axon Ivy Engine via ConfigMaps. However, this also means that the configurations are read-only. During the migration to LTS 10.0, configurations are read from the system database and written to the configuration directory (ivy.yaml, app.yaml and more). The Axon Ivy Engine requires write access for this. The following procedure must therefore be selected:
- Shut down all Axon ivy Engine pods
- Update the Axon Ivy Engine pod to 10.0 and do not make any configurations available via
ConfigMaps.
- Deploy the new pod, but do not scale up. Only one Axon ivy Engine must run during the migration.
- Copy configurations to the container at runtime. Copy all configurations provided as
ConfigMaps to the pod.
- Perform the migration using the Migration Wizard
- Once the migration is complete, back up the
configuration directory and import the new configurations into the ConfigMaps
With Axon Ivy 12.0 we will support the migration of read-only configurations in the migration wizard. The migration wizard asks whether the changes should be made in the current configuration directory or whether the changes should be written to a temporary directory.
