Pre-Upgrade Checks
Check Current Version
Confirm the currently running package version, image tag, database migration version, and Console UI version. Record the current entry domain name, deployed nodes, and upstream model services.
Check Service Status
Confirm that gateway services, PostgreSQL, entry proxy, and upstream model services are healthy before upgrade. Do not start an upgrade while the existing environment is already abnormal.
Check Change Content
Read the release notes and identify whether the target version includes database migration, Route Policy changes, credential changes, Console UI changes, or LobsterPool-compatible entry changes.
Check Backup Conditions
Complete the following checks before the upgrade.
| Check Item | Requirement |
|---|---|
| Version | Source version, target version, release notes, and package checksum have been confirmed |
| Database | PostgreSQL can be connected from the gateway host, and backup has completed successfully |
| Disk | Application directory, log directory, and backup directory have sufficient free space |
| Port | Management port, model invocation port, metric port, and health check port are not occupied by unexpected processes |
| Configuration | Environment variables, configuration files, TLS certificates, and upstream model service addresses have been backed up |
| Traffic | Upgrade window has been approved, and entry-layer routing can be adjusted if rollback is required |
| Monitoring | Health check, metrics collection, and alert receivers are working |
| Credentials | Database account, image registry credential, and operations account are available |