k-space/kube
12
1
Fork 3
Code Issues 61 Pull Requests 1 Wiki Activity

dragonfly: scale to 1 instance (hotfix)

Browse Source 
eaas: dragonfly has 1 rw instance and applications
don't realize and change over from ro to rw when
the leader changes.
This commit is contained in:
rasmus
2025-07-17 10:52:21 +03:00
parent 130839ff7f
commit efb467e425
6 changed files with 6 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
dragonfly-operator-system/README.md
View File

@@ -1,5 +1,4 @@
# Dragonfly Operator
Dragonfly operator is the preferred way to add Redis support to your application
as it is modern Go rewrite and it supports high availability.
@@ -14,9 +13,7 @@ Note that vanilla Redis
[has changed it's licensing policy](https://redis.io/blog/redis-adopts-dual-source-available-licensing/)
# For users
Refer to [official documentation on usage](https://www.dragonflydb.io/docs/getting-started/kubernetes-operator#create-a-dragonfly-instance-with-replicas)
For example deployment see
[here](https://git.k-space.ee/k-space/kube/src/branch/master/passmower/dragonfly.yaml).
To find other instances in this repository use `grep -r "kind: Dragonfly"`
@@ -27,7 +24,3 @@ To achieve high availabilllity use 2+ replicas with correctly configured
# For administrators
See [/argocd/applications/dragonfly.yaml](/argocd/applications/dragonfly.yaml)
To upgrade refer to
[github.com/dragonflydb/dragonfly-operator](https://github.com/dragonflydb/dragonfly-operator/releases),
bump version and reapply