dragonfly-operator

Dragonfly Operator manages the lifecycle of DragonflyDB instances on Kubernetes, providing automated provisioning, failover, scaling, and management of in-memory datastores. The Dragonfly Operator Helm chart automates deployment and configuration of the DragonflyDB Operator in Kubernetes clusters using the Minimus Dragonfly Operator images.

Prerequisites

A subscription to the Minimus images included in the chart
A running Kubernetes cluster (v1.21 or higher is recommended)
kubectl installed and configured
Helm v3.8 or higher for OCI support (Installation instructions)
Cluster Admin privileges

Note: The Dragonfly Operator requires CRDs to be installed in the cluster. The chart installs them automatically by default (crds.install: true).

Try It Out

In this example we will deploy the DragonflyDB Operator on a Kubernetes cluster using the Minimus Dragonfly Operator Helm chart. The operator will be ready to manage DragonflyDB instances.

Step 1: Start Cluster

If you have a cluster to work with, skip this step. Otherwise, start a Minikube cluster. Deployment instructions

Step 2: Create Namespace

Create a namespace:

kubectl create ns dragonfly-operator

Step 3: Deploy the Helm Chart

Deploy the Minimus Helm chart:

helm install my-dragonfly-operator oci://helm.mini.dev/dragonfly-operator \
  --version v1.5.0 \
  -n dragonfly-operator \
  --wait

If you want to override the chart's defaults, go to the Values tab, save a copy locally with your changes. Deploy the chart with your overrides using -f values.yaml:

helm install my-dragonfly-operator oci://helm.mini.dev/dragonfly-operator \
  --version v1.5.0 \
  -f values.yaml \
  -n dragonfly-operator \
  --wait

Step 4: Verify Dragonfly Operator is Running

Confirm the chart deployed successfully and the operator started:

kubectl get pods -n dragonfly-operator

You should see output similar to:

NAME                                                          READY   STATUS    RESTARTS   AGE
my-dragonfly-operator-dragonfly-operator-xxxxxxxxx-xxxxx      2/2     Running   0          2m

The pod should show 2/2 containers ready for the operator manager and the kube-rbac-proxy sidecar.

Step 5: Create a DragonflyDB Instance

Now that the operator is running, you can create a DragonflyDB instance managed by it.

Save the following custom resource to a file called dragonfly-sample.yaml:

apiVersion: dragonflydb.io/v1alpha1
kind: Dragonfly
metadata:
  name: dragonfly-sample
  namespace: dragonfly-operator
spec:
  replicas: 2
  resources:
    requests:
      cpu: 500m
      memory: 500Mi
    limits:
      cpu: 600m
      memory: 750Mi

Apply it to the cluster:

kubectl apply -f dragonfly-sample.yaml

Wait for the instance to become ready, then verify its status:

kubectl get dragonflies.dragonflydb.io -n dragonfly-operator

Step 6: Clean Up

Uninstall the chart and delete the namespace to remove all resources:

helm uninstall my-dragonfly-operator -n dragonfly-operator
kubectl delete namespace dragonfly-operator

Terms & Info

Trademark

This catalog is published by Minimus. All product names, logos, and marks, other than those belonging to Minimus, shown are owned by their respective rights holders and appear here only to identify the open source software each image contains. Minimus claims no ownership of those marks and implies no affiliation with, endorsement by, certification by, or sponsorship by any rights holder.

Disclaimer

Images are provided "as-is" without warranty of any kind. "Hardened" refers to the security configuration applied at the time of build and does not constitute a guarantee of ongoing security or absence of vulnerabilities. The free tier is provided without support, SLA, or guaranteed patching timelines. Security updates may be applied to paid subscriptions before or instead of free tier images. By pulling or using any image you agree to our Terms of Use.

This page is available on desktop