Skip to main content

Installation

The MSSQL Provider is distributed as a Helm chart from the Solanica OCI registry. The chart bundles the MSSQL Operator as a subchart, so a single install brings up both the provider control plane and the operator that provisions SQL Server.

Private distribution

The MSSQL Provider and its bundled operator are not publicly available — the charts and images live in a private registry. You need access credentials from Solanica to install them. Contact us to request access.

Prerequisites​

  • A Kubernetes cluster (v1.27+) and kubectl
  • Helm v3.8+ (OCI support)
  • OpenEverest CRDs installed (or the Solanica Platform, which installs them for you)
  • cert-manager — required by the bundled operator's webhook and metrics certificates
  • Solanica registry credentials (see Authenticate below)

Authenticate​

Log in to the private registry with the username and access token Solanica provided, and create a matching image pull Secret:

helm registry login ghcr.io \
  --username <your-username> \
  --password <your-access-token>

kubectl create secret docker-registry solanica-registry \
  --docker-server=ghcr.io \
  --docker-username=<your-username> \
  --docker-password=<your-access-token>

Install the provider​

helm install provider-mssql \
  oci://ghcr.io/solanicaio/charts/provider-mssql \
  --version 0.1.0 \
  --create-namespace \
  --set imagePullSecrets[0].name=solanica-registry

This installs the provider controller and, by default, the bundled MSSQL Operator. Verify the pods are running:

kubectl get pods
kubectl get providers.core.openeverest.io

Managing the operator separately​

If you already run the MSSQL Operator (or want to manage it independently), disable the bundled subchart:

helm install provider-mssql \
  oci://ghcr.io/solanicaio/charts/provider-mssql \
  --version 0.1.0 \
  --set operator.enabled=false

Upgrade​

helm upgrade provider-mssql \
  oci://ghcr.io/solanicaio/charts/provider-mssql \
  --version 0.1.0

Uninstall​

helm uninstall provider-mssql

Uninstalling does not delete existing Instance resources or their storage — remove those separately to reclaim resources.

Next steps​