You are looking at the documentation of a prior release. To read the documentation of the latest release, please
visit here.
New to KubeDB? Please start here.
Restart Ignite
KubeDB supports restarting the Ignite database via a IgniteOpsRequest. Restarting is useful if some pods are got stuck in some phase, or they are not working correctly. This tutorial will show you how to use that.
Before You Begin
At first, you need to have a Kubernetes cluster, and the kubectl command-line tool must be configured to communicate with your cluster. If you do not already have a cluster, you can create one by using kind.
Now, install KubeDB cli on your workstation and KubeDB operator in your cluster following the steps here.
To keep things isolated, this tutorial uses a separate namespace called
demothroughout this tutorial.
$ kubectl create ns demo
namespace/demo created
Note: YAML files used in this tutorial are stored in docs/examples/ignite folder in GitHub repository kubedb/docs.
Deploy Ignite
In this section, we are going to deploy a Ignite database using KubeDB.
apiVersion: kubedb.com/v1alpha2
kind: Ignite
metadata:
name: ig
namespace: demo
spec:
version: "2.17.0"
replicas: 3
storageType: Durable
storage:
storageClassName: "standard"
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 1Gi
deletionPolicy: WipeOut
Let’s create the Ignite CR we have shown above,
$ kubectl create -f https://github.com/kubedb/docs/raw/v2026.2.16-rc.0/docs/examples/ignite/restart/ig.yaml
ignite.kubedb.com/ig created
Apply Restart opsRequest
apiVersion: ops.kubedb.com/v1alpha1
kind: IgniteOpsRequest
metadata:
name: restart
namespace: demo
spec:
type: Restart
databaseRef:
name: ig
timeout: 3m
apply: Always
spec.typespecifies the Type of the ops Requestspec.databaseRefholds the name of the Ignite database. The db should be available in the same namespace as the opsRequest- The meaning of
spec.timeout&spec.applyfields will be found here
Note: The method of restarting the standalone & clustered ignite is exactly same as above. All you need, is to specify the corresponding Ignite name in
spec.databaseRef.namesection.
Let’s create the IgniteOpsRequest CR we have shown above,
$ kubectl create -f https://github.com/kubedb/docs/raw/v2026.2.16-rc.0/docs/examples/ignite/restart/ops.yaml
igniteopsrequest.ops.kubedb.com/restart created
Now the Ops-manager operator will restrart the pods sequetially by their cardinal suffix.
$ kubectl get igniteopsrequest -n demo
NAME TYPE STATUS AGE
restart Restart Successful 10m
$ kubectl get igniteopsrequest -n demo -oyaml restart
apiVersion: ops.kubedb.com/v1alpha1
kind: IgniteOpsRequest
metadata:
annotations:
kubectl.kubernetes.io/last-applied-configuration: |
{"apiVersion":"ops.kubedb.com/v1alpha1","kind":"IgniteOpsRequest","metadata":{"annotations":{},"name":"restart","namespace":"demo"},"spec":{"apply":"Always","databaseRef":{"name":"mongo"},"readinessCriteria":{"objectsCountDiffPercentage":15,"oplogMaxLagSeconds":10},"timeout":"3m","type":"Restart"}}
creationTimestamp: "2022-10-31T08:54:45Z"
generation: 1
name: restart
namespace: demo
resourceVersion: "738625"
uid: 32f6c52f-6114-4e25-b3a1-877223cf7145
spec:
apply: Always
databaseRef:
name: ig
timeout: 3m
type: Restart
status:
conditions:
- lastTransitionTime: "2022-10-31T08:54:45Z"
message: Ignite ops request is restarting the database nodes
observedGeneration: 1
reason: Restart
status: "True"
type: Restart
- lastTransitionTime: "2022-10-31T08:57:05Z"
message: Successfully Restarted ReplicaSet nodes
observedGeneration: 1
reason: RestartReplicaSet
status: "True"
type: RestartReplicaSet
- lastTransitionTime: "2022-10-31T08:57:05Z"
message: Successfully restarted all nodes of Ignite
observedGeneration: 1
reason: Successful
status: "True"
type: Successful
observedGeneration: 1
phase: Successful
Cleaning up
To cleanup the Kubernetes resources created by this tutorial, run:
kubectl delete igniteopsrequest -n demo restart
kubectl delete ignite -n demo ig
kubectl delete ns demo
Next Steps
- Detail concepts of Ignite object.
- Monitor your Ignite database with KubeDB using out-of-the-box Prometheus operator.
- Monitor your Ignite database with KubeDB using out-of-the-box builtin-Prometheus.
- Detail concepts of Ignite object.
- Want to hack on KubeDB? Check our contribution guidelines.