Skip to content

Change in spec.resources.limits.cpu not reconciled #367

Description

@ggerrit

After successfully deploying a Valkey object, changing the spec.resources.limits.cpu is not reflected in the StatefulSet.

Steps to reproduce:

  1. 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
  1. Wait until deployed
  2. 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
  1. Expected: the spec.resources.limits.cpu is changed in the StatefulSetby the operator.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions