After successfully deploying a Valkey object, changing the spec.resources.limits.cpu is not reflected in the StatefulSet.
Steps to reproduce:
- Deploy valkey object:
kubectl create -f - <<EOF
---
apiVersion: hyperspike.io/v1
kind: Valkey
metadata:
labels:
app.kubernetes.io/name: keyval
name: keyval
spec:
resources:
limits:
cpu: 200m
memory: 128Mi
requests:
cpu: 100m
memory: 128Mi
EOF
- Wait until deployed
- Then change the settings:
kubectl apply -f - <<EOF
---
apiVersion: hyperspike.io/v1
kind: Valkey
metadata:
labels:
app.kubernetes.io/name: keyval
name: keyval
spec:
resources:
limits:
cpu: 400m
memory: 128Mi
requests:
cpu: 100m
memory: 128Mi
EOF
- Expected: the
spec.resources.limits.cpu is changed in the StatefulSetby the operator.
After successfully deploying a
Valkeyobject, changing thespec.resources.limits.cpuis not reflected in theStatefulSet.Steps to reproduce:
spec.resources.limits.cpuis changed in theStatefulSetby the operator.