Versions
The provider ships a curated catalog of SQL Server versions. Select one with
spec.version on the Instance; if omitted, the default is used.
spec.version | SQL Server | Image | Default |
|---|---|---|---|
2025 | 2025 CU9 | mcr.microsoft.com/mssql/server:2025-CU9-ubuntu-24.04 | ✅ |
2022 | 2022 CU27 | mcr.microsoft.com/mssql/server:2022-CU27-ubuntu-22.04 | |
2019 | 2019 CU32 GDR11 | mcr.microsoft.com/mssql/server:2019-CU32-GDR11-ubuntu-20.04 |
spec:
providerRef:
name: mssql
version: "2022"
Images are pinned to a cumulative update (CU), so a pod restart never pulls a
different build. New CUs are adopted deliberately in provider releases. The
floating 2025-latest, 2022-latest and 2019-latest entries from earlier
releases are kept as deprecated aliases of the pinned builds, so existing
Instances keep resolving.
Native S3 backups (BACKUP ... TO URL) and Contained Availability Groups
require SQL Server 2022 or later. If you need backup & restore,
choose 2022 or 2025; enabling backups on a 2019 Instance is rejected.
Changing the version
To upgrade, set spec.version to a newer release (for example 2022 → 2025).
The pods roll onto the new image and SQL Server upgrades the databases when it
first opens them. Availability Groups are upgraded with the primary last; see the
operator's Version upgrade.
Downgrades are rejected. Databases upgraded by a newer SQL Server release
cannot be opened by an older one, so moving an Instance to an older release (for
example 2025 → 2022) puts it in the Failed phase and leaves the running
deployment untouched. Set spec.version back to recover, or restore a backup
into a new Instance to move to an older release.
Editions
Independently of the version, choose a SQL Server edition per instance under
spec.components.engine.parameters.edition:
| Edition | Licensed | Notes |
|---|---|---|
Developer (default) | Free (non-production) | Full feature set; not for production use |
Express | Free | Feature-limited; standalone only (no Availability Groups) |
Standard | Paid | Supports Always-On Availability Groups |
Enterprise | Paid | Full feature set |
EnterpriseCore | Paid | Enterprise, core-based licensing |
Licensing and compliance are your responsibility. For the full mechanics of how editions are applied, see the operator's CR Reference.