Finish standalone

Signed-off-by: Neaj Morshad <[email protected]>

docs/examples/mssqlserver/reconfigure/ms-standalone.yaml

@@ -0,0 +1,25 @@
+apiVersion: kubedb.com/v1alpha2
+kind: MSSQLServer
+metadata:
+  name: ms-standalone
+  namespace: demo
+spec:
+  version: "2022-cu12"
+  configSecret:
+    name: ms-custom-config
+  replicas: 1
+  tls:
+    issuerRef:
+      name: mssqlserver-ca-issuer
+      kind: Issuer
+      apiGroup: "cert-manager.io"
+    clientTLS: false
+  storageType: Durable
+  storage:
+    storageClassName: "standard"
+    accessModes:
+      - ReadWriteOnce
+    resources:
+      requests:
+        storage: 1Gi
+  deletionPolicy: WipeOut

docs/examples/mssqlserver/reconfigure/msops-reconfigure-standalone-apply.yaml

@@ -0,0 +1,16 @@
+apiVersion: ops.kubedb.com/v1alpha1
+kind: MSSQLServerOpsRequest
+metadata:
+  name: msops-reconfigure-standalone-apply
+  namespace: demo
+spec:
+  type: Reconfigure
+  databaseRef:
+    name: ms-standalone
+  configuration:
+    applyConfig:
+      mssql.conf: |-
+        [memory]
+        memorylimitmb = 3072
+  timeout: 5m
+  apply: IfReady

docs/examples/mssqlserver/reconfigure/msops-reconfigure-standalone.yaml

@@ -0,0 +1,14 @@
+apiVersion: ops.kubedb.com/v1alpha1
+kind: MSSQLServerOpsRequest
+metadata:
+  name: msops-reconfigure-standalone
+  namespace: demo
+spec:
+  type: Reconfigure
+  databaseRef:
+    name: ms-standalone
+  configuration:
+    configSecret:
+      name: new-custom-config
+  timeout: 5m
+  apply: IfReady

docs/guides/mongodb/reconfigure/overview.md

@@ -45,7 +45,7 @@ The Reconfiguring MongoDB process consists of the following steps:
 
 6. When it finds a `MongoDBOpsRequest` CR, it halts the `MongoDB` object which is referred from the `MongoDBOpsRequest`. So, the `KubeDB` Provisioner  operator doesn't perform any operations on the `MongoDB` object during the reconfiguring process.  
 
-7. Then the `KubeDB` Ops-manager operator will replace the existing configuration with the new configuration provided or merge the new configuration with the existing configuration according to the `MogoDBOpsRequest` CR.
+7. Then the `KubeDB` Ops-manager operator will replace the existing configuration with the new configuration provided or merge the new configuration with the existing configuration according to the `MongoDBOpsRequest` CR.
 
 8. Then the `KubeDB` Ops-manager operator will restart the related PetSet Pods so that they restart with the new configuration defined in the `MongoDBOpsRequest` CR.
 

docs/guides/mssqlserver/reconfigure/_index.md

@@ -0,0 +1,10 @@
+---
+title: Reconfigure
+menu:
+  docs_{{ .version }}:
+    identifier: ms-reconfigure
+    name: Reconfigure
+    parent: guides-mssqlserver
+    weight: 67
+menu_name: docs_{{ .version }}
+---