Skip to main content

Release Notes

Version history for the MSSQL Provider, newest first. Versions follow the chart published to the Solanica registry (oci://ghcr.io/solanicaio/charts/provider-mssql). Each release bundles a specific MSSQL Operator version.

v0.1.14 — 2026-10-16​

Bundles MSSQL Operator v0.1.14.

  • Operator v0.1.14: Availability Group failover improvements from fault-injection testing: planned handover before SQL Server stops, clean SQL Server shutdown on pod termination, failover as soon as the primary Lease expires, and Lease-based handling of a stale primary after a network partition. See the operator release notes.
  • Operator v0.1.13: an Availability Group Instance becomes Ready without TLS settings on the Instance, which is how the provider creates it.
Upgrading to v0.1.14

SQL Server pods restart once after the upgrade, because the operator adds preStop hooks to the pod template. For an Availability Group, expect a short write pause while the primary restarts. See the operator upgrade note.

v0.1.13 — 2026-10-14​

Bundles MSSQL Operator v0.1.12.

  • Backups to S3 with a private CA. If the BackupStorage credentials Secret contains a ca.crt key, the provider passes it to SQL Server, so backups work with endpoints signed by a private CA. http:// endpoints are rejected with an InvalidEndpoint error, as SQL Server's BACKUP ... TO URL needs HTTPS. See Backup & Restore.
  • Availability Group Ready status. An Availability Group Instance reports Initializing until the availability group is up, instead of Ready as soon as its pods are.
  • Operator v0.1.12: faster, less disruptive recovery after losing a replica, and monitoring with SA passwords containing URL-reserved characters.

v0.1.12 — 2026-10-13​

Bundles MSSQL Operator v0.1.11.

  • Pinned SQL Server images. Each version now resolves to a specific cumulative update instead of a floating -latest tag: 2025 → 2025 CU9, 2022 → 2022 CU27, 2019 → 2019 CU32 GDR11. The old -latest entries remain as deprecated aliases. See Versions.
  • Downgrades are rejected. Moving an Instance to an older SQL Server release (for example spec.version 2025 → 2022) puts it in the Failed phase and leaves the running deployment untouched, instead of breaking the databases.
  • Scale-down is rejected. Lowering components.engine.replicas on a deployed Instance fails validation with a clear message rather than an operator-level error.
  • Backups on SQL Server 2019 are rejected up front. S3 backups need SQL Server 2022 or later; enabling them on a 2019 Instance now fails validation instead of failing at backup time.
  • Connection URI escaping. The uri in the <name>-conn Secret URL-encodes the SA password, so passwords with characters such as #, % or @ produce a valid URI. See Connecting.
  • Operator v0.1.11: SA password rotation, safe version upgrades (Availability Groups upgrade primary-last, downgrades rejected at admission), and pod labels. See the operator release notes.
Upgrading to v0.1.12

Existing Instances move from the floating -latest image to the pinned CU build of the same release, so their pods roll once after the upgrade. Instances on 2019 with backups enabled fail validation until backups are disabled or the Instance is moved to 2022 or later.

v0.1.11 — 2026-10-07​

Bundles MSSQL Operator v0.1.10.

  • Scheduling policy. The engine honours the platform's scheduling policy (affinity, node selectors, tolerations, topology spread), configurable in the UI.

v0.1.10 — 2026-09-24​

Bundles MSSQL Operator v0.1.9.

  • Default presets. The provider ships instance presets, including a production-grade Availability Group with higher CPU, memory and storage.
  • Separate storage volumes. Data, logs and tempdb can be placed on separate volumes.

v0.1.9 — 2026-09-18​

Bundles MSSQL Operator v0.1.9.

  • Edition and topology changes. Move an Instance to a higher edition, or from standalone to availabilityGroup.
  • Custom configuration. Pass extra mssql.conf settings through to SQL Server. See Configuration.

v0.1.2 — 2026-08-29​

  • Monitoring. Enable metrics and a PodMonitor from the Instance.
  • Validation that a standalone Instance runs a single replica.

v0.1.1 — 2026-08-28​

  • Status reporting aligned with the MSSQL Operator v0.1.8 status fields.

v0.1.0 — 2026-08-28​

  • Initial release: SQL Server as an OpenEverest Instance with standalone and availabilityGroup topologies, curated versions, and native backup & restore with point-in-time recovery.