Open xEBIx opened 6 months ago
@Pothulapati can you pls take a look?
I'm able to get the operator (dragonflydb/operator:v1.1.2
) to run on ARM64 but not the cluster (dragonflydb/dragonfly:v1.17.1
).
---
# yaml-language-server: $schema=https://kubernetes-schemas.pages.dev/dragonflydb.io/dragonfly_v1alpha1.json
apiVersion: dragonflydb.io/v1alpha1
kind: Dragonfly
metadata:
name: dragonfly
spec:
image: ghcr.io/dragonflydb/dragonfly:v1.17.1
replicas: 3
env:
- name: MAX_MEMORY
valueFrom:
resourceFieldRef:
resource: limits.memory
divisor: 1Mi
args:
- --maxmemory=$(MAX_MEMORY)Mi
- --proactor_threads=2
- --cluster_mode=emulated
- --lock_on_hashtags
resources:
requests:
cpu: 100m
limits:
memory: 512Mi
dragonfly-0
status:
State: Waiting
Reason: CrashLoopBackOff
Last State: Terminated
Reason: Error
Exit Code: 132
Describe the bug I installed dragonfly with the following command from your Webpage: helm upgrade -n dragonfly --install dragonfly oci://ghcr.io/dragonflydb/dragonfly/helm/dragonfly --version v1.13.0 (https:///dragonfly-6d7www.dragonflydb.io/docs/getting-started/kubernetes#more-customization)
I get the following shown by kubectl -n dragonfly get all
And also the command kubectl -n dragonfly logs (-p) dragonfly-6d7d5b6bb4-rszth returns nothing.
To Reproduce Execute helm upgrade -n dragonfly --install dragonfly oci://ghcr.io/dragonflydb/dragonfly/helm/dragonfly --version v1.13.0 on your arm cluster.
Expected behavior Drogonfly Pod running.
Environment (please complete the following information):
6.10
helm output (--dry-run)
The same issue resides when using the operator or a default values.yaml.