From 4.0.3-fp3 to 4.1.0
Summary
Optimization Server 4.1.0 introduces changes in
Helm charts
master API
Development of applications
| Library | Backward compatibility | Deprecations |
|---|---|---|
| Master API client | Backward compatible | |
| Worker (Java) | Backward compatible | |
| Worker (Python) | Backward compatible |
Deployment of Optimization Server
| Chart | Backward compatibility | Deprecations |
|---|---|---|
| dbos-volume | Backward compatible | |
| dbos-secrets | Break changes | |
| dbos-infra | Break changes | |
| dbos | Break changes | |
| cplex | Backward compatible | |
| wod | Backward compatible |
Helm charts
dbos-secrets and related charts
The admin credentials of Rabbit and Postgres and Mongo and Keycloak have been changed. If you want to update an existing environment, please follow the instructions below. New environments are not concerned by this migration procedure.
Important note: Before any manipulation, make sure to backup all deployed secrets !
When redeploying, you should be used to reuse the deployed secrets but a new one has been introduced to hold the Keycloak admin username. It's configurable with the following values for the dbos-secrets chart:
keycloak:
adminUsername: ...To deploy this new secret, you must redeploy the dbos-secret chart with the credentials that your deployed secrets contain. You have to create a values file for the dbos-secret chart with all your secrets (in clear text, see details in the this page) then use this values file to deploy the dbos-secret chart.
Master API
A changes have been made in the Optimization Server master API in order to support empty job inputs. Before 4.1.0, an input that contains no data (empty string or zero byte) was dropped so it was null at worker level. Starting from 4.1.0, such inputs are kept and are not null at worker level.