Standalone
The standalone topology deploys a single, independent SQL Server instance
with no replication. It maps to the operator's
MSSQLInstance resource.
Use it for development, testing, and single-server workloads that don't require high availability.
Example
apiVersion: core.openeverest.io/v1alpha1
kind: Instance
metadata:
name: example-instance
spec:
providerRef:
name: mssql
version: "2022"
topology:
type: standalone
components:
engine:
replicas: 1
resources:
limits:
cpu: "1"
memory: 2Gi
storage:
size: 10Gi
# External access: creates an additional "<name>-exposed" Service.
service:
serviceType: LoadBalancer
annotations: {}
loadBalancerService:
sourceRanges: []
parameters:
edition: Developer
Configuration
| Field | Notes |
|---|---|
components.engine.replicas | Fixed at 1 for standalone. |
components.engine.resources.limits | CPU (min 1) and memory (min 2Gi). |
components.engine.storage.size | Disk size; cannot be decreased on update. |
components.engine.service.serviceType | ClusterIP, LoadBalancer, or NodePort. |
components.engine.parameters.edition | Developer, Express, Standard, Enterprise, or EnterpriseCore. |
note
Express edition is available for standalone instances but not for
Availability Groups.
Connecting
Once the instance is ready, connect to it as described in Connecting.
See also
- Availability Group — the HA topology.
- Operator:
MSSQLInstancereference.