About Migrate Job
Every time Cloudentity starts up, it checks SQL data for new migrations. This operation takes an extra time on every startup (i.e autoscaling) before Cloudentity serves user requests. Additionaly, during upgrade procedure or in the multi-region scenario, multiple Cloudentity instances can start migrations at the same time which can lead to restarts due tp the SQL table lock. To mitigate this issues, migration job was introduced.
- Kubernetes cluster v1.16+
- Helm v3.0+
Configure Migrate Job
The migrate job creates a Helm hook to create K8s job which utilizes Cloudentity the sql migrate command. At the same time, migrations check is disabled on Cloudentity startup.
Enable migrate job
migrateJob: enabled: true
Migration job uses
sql.url as a SQL endpoint. Additionally it uses configuration provided in
secret config. You can provide
additional parameters via
Increase SQL migration timeout
migrateJob: config: sql: migrations: timeout: 10m
Cloudentity could be integrated with timescale to store audit events. This functionality is disabled by default. If you use timescale integration, you should enable migrate job for it. If you store your timescale url parameter in secret, it will be picked up automatically.
Enable migration job for timescale
migrateJob: config: timescale: enabled: true url: "postgres://firstname.lastname@example.org:5432/acpdb?sslcert=%2Ftls%2Ftls.crt&sslkey=%2Ftls%2Ftls.key&sslmode=verify-full&sslrootcert=%2Ftls%2Fca.crt"